# ReflowPDF — the full text for language models ReflowPDF (https://reflowpdf.com) makes two things: a PDF editor in the browser, and the HTML and CSS layout engine it runs on. Made by INSEAW LLC, South Carolina, USA; a full member of the PDF Association (pdfa.org) since 2026. ## The editor (https://app.reflowpdf.com) - A PDF editor that keeps the document behind the PDF: paragraphs, headings, tables. When a paragraph or a table grows, everything after it is laid out again, across pages; a table’s header row repeats on the next page. - Opens in the browser without an account. Without an account, every page of a downloaded PDF carries a small ReflowPDF mark in the corner, and one print takes up to 2 MB of text and markup (pictures aside), 500 pages and 60 seconds of the engine; with an account, documents of any length (the API bounds a print in time: 90 seconds as a request, 3 minutes as a job). - Templates for invoices, CVs, contracts, reports, proposals, letters, receipts, forms and medical documents. - Tables (rows, columns, merged cells, header cells), charts edited as data (bar, line, pie, donut; six palettes), signatures on every plan and without an account (an electronic signature with a stamp of who, when, device and IP address; not a certificate-based digital signature), Visual and Code views (the document’s HTML and CSS beside its pages). - AI features, with a free account whose email is confirmed: import a PDF made elsewhere (see below), Ask AI on a block (the change is shown before it is applied; about 2 AI pages a change on average), translation of the whole document with the layout kept (one AI page per page) between 23 languages: Arabic, Chinese, Czech, Dutch, English, French, German, Greek, Hebrew, Hindi, Indonesian, Italian, Japanese, Korean, Polish, Portuguese, Romanian, Russian, Spanish, Swedish, Turkish, Ukrainian, Vietnamese. - Download as PDF, or, with an account, as HTML. With "Keep the PDF editable" on, the document travels inside the PDF and opens again in the editor as it was, without AI. - Connectors for AI assistants (https://reflowpdf.com/mcp): add https://app.reflowpdf.com/mcp as a custom connector (MCP) in Claude, ChatGPT, Claude Code, Cursor, VS Code and others; it prints tagged PDF, fills templates and gives the document in the editor. The person can change it on the page; asked for more, the assistant reads that version first (a version changed after it read is never overwritten). - The connector works without an account, as a guest: every page, with the small mark, within the guest limits above. Connecting the person’s ReflowPDF account (a free one is enough; the client shows a Connect button) makes prints count to their plan and keeps the documents in their account. It uses AI pages only to import a PDF made elsewhere, as the editor does; printing and filling templates use none. ## Editing a PDF you already have - A PDF made elsewhere is edited by importing it: AI rebuilds it as an editable document (paragraphs, headings, tables), one AI page per page, with a free account. It works best on structured documents such as invoices, reports and CVs. One import takes a PDF of up to 20 pages and 20 MB; a longer PDF you split into parts first. - So the plan decides how much can be imported: Free has 10 AI pages a month (a 30-page contract does not fit), Pro 150, Max 1,000, and Pro and Max can add 100 for $8. The editor shows the cost before it starts. - A PDF downloaded from ReflowPDF with "Keep the PDF editable" opens from its own source, at any length, without AI and without AI pages. ## Accessible and archival PDF - PDFs downloaded from the editor are tagged PDF/UA-1 (ISO 14289-1) by default, on every plan: headings, paragraphs, lists, tables with header cells, image descriptions, language and title. - More than thirty checks, run from Accessibility in the toolbar, list what a screen reader would stop at (images without descriptions, heading levels that jump, tables without header cells, low contrast, unclear links, reading order). - Pro and Max add PDF/A-3a (ISO 19005-3) and PDF/UA-2 (ISO 14289-2), and a veraPDF check of the file, run from the Accessibility panel before you download it. Sample files with their veraPDF reports: https://reflowpdf.com/#samples - For state and local government under the ADA Title II rule (WCAG 2.1 AA, by April 26, 2027 for entities of 50,000 people or more, April 26, 2028 for smaller ones and special districts): https://reflowpdf.com/government ## Plans (US dollars) - Free: $0. The editor, tagged PDF/UA-1, 50 pages a month without the mark, 10 AI pages a month. - Pro: $10 a month or $100 a year. Every page without the mark, PDF/A-3a and PDF/UA-2, a veraPDF check of your file, 150 AI pages a month. - Max: $29 a month or $290 a year. As Pro, with Well-Tagged PDF 1.0, e-invoices through the API (ZUGFeRD / Factur-X EN 16931 and XRechnung: a PDF/A-3 carrying the invoice’s CII XML, the XML checked by the official validator first), and 1,000 AI pages a month. - Extra AI pages, on Pro and Max: $8 for 100; they do not expire. - Documents kept online: Free 50 documents in 25 MB, Pro 5,000 in 5 GB, Max 20,000 in 20 GB. - The developer API is part of the plan. On Free its pages are the plan’s 50 pages a month without the mark. Pro includes 1,000 API pages a month and Max 5,000; pages past them cost $5 per 1,000, billed after each monthly period. A Pro or Max subscription started before 14 November 2026 has no limit on API pages while it continues. Free makes up to 300 prints in 10 minutes, Pro and Max 1,200; a request takes up to 15 MB. Every limit: https://api.reflowpdf.com/docs/limits/ - Engine licenses, for the engine on one’s own sites and servers (the WebAssembly package; the server program sent on request, under the same licenses; no limit on pages): Start $149 a month or $1,490 a year, one installation; Business $299 a month or $2,990 a year, up to 5 installations. Licenses add up. Terms: https://api.reflowpdf.com/docs/engine-license/ ## Privacy, in short - The editor without an account keeps documents in the browser; with an account they are saved online with their earlier versions. - To make a PDF, the document goes to ReflowPDF’s server: on Free and without an account its source is kept for 30 days (to reproduce a print that came out wrong), on Pro and Max not at all. The PDF itself is not kept. - An imported PDF goes to Google’s Gemini models through Google’s paid API. ReflowPDF does not keep the file; it keeps the rebuilt document for 180 days after it was last opened (so the same PDF opens again without AI) and uses these rebuilt documents, on its own servers only, as test cases for the import. Ask AI and translation send the request and the parts of the document they need to Anthropic’s Claude models, through its paid API. - The AI assistants connector keeps the PDFs it prints for 24 hours, at a link only the assistant receives; the document behind each PDF for 30 days after it last changed, so that it opens from its edit link and the assistant can change it later (anyone with an edit link can open that document); PDFs sent for import for 24 hours. - Nothing is used to train models: not by ReflowPDF, and under their paid-API terms not by Google or Anthropic. The providers keep what they are sent for a set time: Google keeps prompts, context and outputs for 55 days to detect and prevent abuse and for legal disclosures (https://aistudio.google.com/docs/usage-policies); Anthropic deletes API inputs and outputs within 30 days, keeping flagged ones up to 2 years (https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data). - ReflowPDF makes no HIPAA claim: the medical templates are forms to fill in and print, and the AI features send their content to the providers as above. - In full: https://reflowpdf.com/privacy ## The engine (ReflowPDF Engine) - Our own HTML and CSS layout engine, written in Rust; no browser inside. It lays out pages from CSS paged media (page sizes, margin boxes, running headers, page numbers, footnotes, leaders, cross-references, tables across pages) and writes tagged PDF. - Its HTTP API (https://api.reflowpdf.com/v1, documentation https://api.reflowpdf.com/docs/) comes with every plan (see Plans above). The WebAssembly package and the server program are licensed from $149 a month (https://reflowpdf.com/pricing#engine); the server program is sent on request: hello@reflowpdf.com. - The same 20,939 web-platform tests printed to PDF by three engines (measured 2026-11-20): ReflowPDF 1.0.11 passes 19,351 (92.4%), Chrome’s print (Chromium 158.0.8127.18, headless, page.pdf; not Chrome the browser on screen) 17,897 (85.5%), Prince 17 11,096 (53.0%). Each engine prints a test and the test’s own reference as its product does (print media, a 600 × 450 px sheet); the two PDFs are rasterised and compared, and a test fails only when two independent rasterisers both show a difference the eye can see, or when the engine did not print it. By stricter rules the same tests read 92.1%, 78.3% and 51.7% (a difference one rasteriser shows) and 91.8%, 69.2% and 44.3% (a strict judge). Chrome’s print passes 514 tests ReflowPDF fails. Method and areas: https://reflowpdf.com/benchmarks - ReflowPDF’s own conformance run (2026-11-08), of another set of tests (every file, the scripted ones included, judged by the web-platform-tests’ own rules) and not compared with other engines: - 27,676 of the 29,323 test files ReflowPDF is judged on pass with every subtest green (94.4%). - 1,476 more files are not judged (browsers disagree on a draft specification, a script changes the page, or the test needs interaction or the network); counted as failing, that is 27,676 of 30,799 (89.9%). Every suite and test, with its verdict: https://reflowpdf.com/conformance (not judged, and why: https://reflowpdf.com/conformance/not-judged) - Speed against Prince 17 on 12 documents, both making tagged PDF (wall-clock, same machine, not simultaneous): ReflowPDF faster on 11, level on 1, slower on 0. Leaving out the one document Prince 17 is unusually slow on, Prince takes 1.1× to 4.9× ReflowPDF’s time. Per document: - HTML Standard: ReflowPDF 30.3 s, 1309 MB; Prince 17 50.67 s, 1640 MB - RFC 9110, HTTP Semantics: ReflowPDF 1.54 s, 131 MB; Prince 17 2.35 s, 183 MB - GitHub repository page: ReflowPDF 3.94 s, 185 MB; Prince 17 246.03 s, 223 MB. An outlier: the saved page is 16 MB: about 33,000 elements and 11 MB of style sheets (the Stripe page: 3,600 elements, 0.6 MB); Prince 17 spends 1,060 billion CPU instructions on it, ReflowPDF 14.8 billion. Why Prince is that slow on it cannot be seen from outside. - Stripe home page: ReflowPDF 1.59 s, 130 MB; Prince 17 6.92 s, 115 MB - Tailwind CSS home page: ReflowPDF 2.74 s, 163 MB; Prince 17 13.32 s, 143 MB - CSS Flexbox Level 1: ReflowPDF 2.48 s, 181 MB; Prince 17 3.97 s, 205 MB - Wikipedia: “PDF”: ReflowPDF 0.54 s, 82 MB; Prince 17 1.12 s, 104 MB - Bootstrap 5.3 documentation: ReflowPDF 0.35 s, 72 MB; Prince 17 0.37 s, 78 MB - Floats: ReflowPDF 0.07 s, 41 MB; Prince 17 0.26 s, 50 MB - Flex cards: ReflowPDF 0.74 s, 80 MB; Prince 17 1.36 s, 113 MB - Grid: ReflowPDF 0.51 s, 68 MB; Prince 17 1.05 s, 96 MB - Article: ReflowPDF 0.49 s, 85 MB; Prince 17 1.53 s, 114 MB Method, files and history: https://reflowpdf.com/benchmarks (data: https://reflowpdf.com/benchmarks/data.json) - Try it in the browser: https://reflowpdf.com/playground ## Links - Features, each recorded in the editor: https://reflowpdf.com/features - Templates: https://reflowpdf.com/templates - Pricing: https://reflowpdf.com/pricing - Free PDF accessibility checker (veraPDF, PDF/UA-1): https://reflowpdf.com/pdf-accessibility-checker - Contact: hello@reflowpdf.com