Cut days off your documentation approval cycle. Give PMs, SMEs, and Legal a visual preview of changes. They can edit, comment, and sign off in minutes. GitHub account, optional for reviewers.
API v3 introduces cursor-based pagination, a new auth header format, and deprecates the /v1/search endpoint in favor of /v3/query.
v1 is deprecated on June 30, 2026. Migrate by then or requests will start returning 410 Gone.
They're scrolling past it. Or asking you to export a Google Doc. Or catching typos after the post is live.
Install once in your repository. Any PR that touches Markdown, MDX, or AsciiDoc gets a review link commented on the PR, ready to share.
Sign in with GitHub and paste any PR URL to instantly open your docs in a clean reading view. Installing the DraftView GitHub App takes 10 seconds, that's all the setup there is.
DraftView handles reviewers with or without GitHub accounts. They open a clean, Google Docs-style canvas and start editing immediately. Lock it down with a password, cap submissions, or require SSO. External reviewers never touch GitHub.
Comments become PR comments. Suggestions become GitHub suggestions. No copy-paste. No reformatting.
Rendered previews. Inline comments. Scoped permissions. Everything you need, nothing you don't.
See the page exactly as it'll ship. Images, typography, callouts, MDX components, all rendered. No more asking “what will this actually look like?”
API v1 is deprecated as of June 30, 2026. Requests will return a 410 Gone status.
No separate access management. If they can see the PR on GitHub, they can see the preview. Invite external stakeholders using secure links, no GitHub required for them.
Every inline comment posts as a GitHub review. No new silo for your team to monitor.
Who approved what, when. Exportable logs. Required reviewers before merge. Built for teams with compliance requirements.
Conversations with technical writers shaped how DraftView works.
Getting PM reviews is the biggest problem for any doc-review workflow. Their feedback is disconnected from the original. If you're using GitHub, your reviewers would all have to understand and be able to smoothly work with the source structure. This is pretty unlikely.
The 'old-fashioned' way is the doc writer has to manually implement the changes back to the source. I've only ever practiced the optimal way where all reviewers have access to GitHub and comment on source files. And that almost never happens.
We hate the duplicative Google Doc 'article to source, then source to doc' situation, but also kind of need it. We don't have a better way available.
I do all my drafting in Google Docs. Although it's not the only reason, Google Docs makes the editorial stage of writing much simpler to get feedback from SMEs and to have your writing undergo review.
I have never encountered someone with access to GitHub who can't get lost in convoluted source structure.
The SME feedback is disconnected from the original source. Your reviewers would all have to understand and smoothly work with the AsciiDoc source structure. This is highly unlikely.
One subscription per repository. Unlimited reviewers.
No credit card required · cancel anytime
What counts as a review?
A review is counted when someone submits feedback. Opening or browsing a PR doesn't count.
After the trial
After 14 days, free tier limits apply automatically. No credit card required to start.
Early Access pricing
Your rate is locked in for 12 months after any price change. No surprises for early supporters.
Everything you need to know about DraftView. If your question isn't here, we're an email away.
Sign in with GitHub and your next PR gets a preview link automatically. Free for public repos. No credit card.