State of docs report 2025
State of docs report 2025
444
Total Respondents, with roles across multiple disciplines
54%
54%
believe their docs generate at least as many leads as their marketing sites
42%
42%
THINk ai will let us build docs that intelligently adapt to user needs
46%
46%
OF large companies have decentralized or hybrid docs teams
Welcome to the State of Docs Report 2025
State of Docs brings together insights from documentation experts from across the industry.
This comprehensive report explores how teams track their docs’ success, the future of the industry, the ongoing impact of AI on documentation, and much more.
With input from expert partners
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
Be part of The State of Docs Report 2026
Interested in helping us get a head-start on the 2026 report?
© 2025 Copyright GitBook INC.
440 N Barranca Ave #7171, Covina, CA 91723, USA. EIN: 320502699
Be part of The State of Docs Report 2026
Interested in helping us get a head-start on the 2026 report?
© 2025 Copyright GitBook INC.
440 N Barranca Ave #7171, Covina, CA 91723, USA. EIN: 320502699
Be part of The State of Docs Report 2026
Interested in helping us get a head-start on the 2026 report?
© 2025 Copyright GitBook INC.
440 N Barranca Ave #7171, Covina, CA 91723, USA. EIN: 320502699