Your paper looks finished. Then a reviewer finds the flaw on page nine — a claim your own results do not support. Deep Review exists to catch that moment before a stranger does.
Google Research launched Deep Review on October 14, 2026, and every user gets two free document reviews per week. This guide shows you how to use Google Deep Review from the first click to the final report, so those two free checks actually count.
What Deep Review actually checks
It is a strict reader, not a proofreader. Deep Review reads a complex document and flags logical gaps, mathematical errors, unsupported claims, and sections that contradict each other.
Dense math gets extra attention. The system gives harder sections more computing power than easy ones, and separate agents check different parts at the same time. A final synthesis stage merges the findings, cross-checks sections against each other, and runs grounding checks.
It grew out of Google’s Paper Assistant Tool, which gave pre-submission feedback on more than 16,000 manuscripts at STOC, ICML, NeurIPS and ICLR. The public version adds Gemini 4 Argon support and now covers design documents, presentations, and legal and financial files too. That range is the honest surprise here.
Step by step: run your first review
Step one: open Deep Review from the Google Research portal and sign in with a Google account. No install. No card. Your two free weekly reviews are tied to that account, and finished reviews wait in a “Your documents” table.
Step two: upload a PDF or paste your text in plain form. A PDF suits a full paper, while pasted text suits one dense chapter. Either way, the PDF needs a real text layer rather than scanned pages, because the tool reads text, not pictures of text.
Step three: fill in the custom context box before you submit. Tell the tool what the document is and what worries you most, like the math in section three or a claim that outruns the data. A plain one-line brief beats an empty box every time.
Step four: submit and walk away. A review takes about 10 to 30 minutes, since the agents work through the document in stages instead of skimming it once. You do not need to keep the tab open.
How to read the report
The report arrives as overall findings plus detailed comments, grouped around logic, math, facts and cross-section consistency. Start with the big findings. Then work down to the small suggestions.
Treat each flag as a lead, not a verdict. Can you spot the problem yourself in the section it names? If not, it may be a false alarm, and changing correct work on a hunch makes things worse. Then click Copy Report to export the review in Markdown and turn it into a revision checklist.
Make two free reviews work like four
Here is the workflow that makes the most sense. Spend review one on your draft, verify each flag with your own eyes, and fix only what truly checks out. Then spend review two on the revised file.
Why burn both reviews on one document? Because a fix in section two can quietly break a claim in section five, and the second pass catches slips your edits added. One caution: Google says uploads are never used to train its models, but they are stored for one year, so skip anything you would not want stored.
Two free checks a week. Use them like a strict friend: early, then once more before you send.
Sources
- https://research.google/blog/analyzing-technical-documents-with-deep-review
- https://aitoolsteps.com/how-to-use-google-deep-review-for-beginners/
- https://phdtalks.org/2026/10/google-deep-review.html