OCR + PDF text
Use a PDF's text layer when possible or recognize scanned pages with open-source Tesseract OCR running locally.
Find words, rebuild text and tables, capture illustrations, then refine everything in an editable page workspace. No paid API or document uploads.
Import, recognize, inspect and refine — all in your browser.
Recognition estimates positions. Correct text, tables and reading order before publishing.
Draw on the page to create regions. Drag existing regions to move them.
Import a scan or use the sample to explore text recognition, table reconstruction and editable regions.
Export document content, not just a screenshot.
DOCX preserves text, tables and captured image regions in reading order; HTML keeps approximate page coordinates. Exact typography and complex layouts require review.
Use a PDF's text layer when possible or recognize scanned pages with open-source Tesseract OCR running locally.
Correct detected paragraphs, convert repeated columns to tables, and manually mark images or diagrams as captured regions.
Create Word documents, position-aware editable HTML, text files and portable JSON projects without uploading originals.
No. Browser OCR and layout heuristics provide an editable first draft, but multi-column documents, merged tables, handwriting and unusual typefaces need review. Scanned images require user-marked image regions.
No. Document images are processed on your device. OCR and PDF libraries, and OCR language data, may download from public CDNs when first needed. Your document contents are not sent to those services by this tool.
Word reflows paragraphs and tables. The HTML export retains approximate absolute page positions, while Word exports prioritize editable content and reading order rather than pixel-perfect positioning.
PDF, PNG, JPEG and WebP sources are supported within the tool's page, dimension and file size limits. A saved PixelOkay JSON project may also be reopened.
Import supported images or a PDF and choose recognition settings. Review text/table blocks, select image crops manually and correct positions or reading order. Save a JSON project before exporting DOCX, HTML or text.
PDF text geometry and table detection are estimates; figures require manual selection. Earlier/Later changes export reading order rather than physical position. DOCX reflows paragraphs/tables and is not a pixel-perfect copy; positioned HTML also depends on fonts/browser rendering. PDF.js/Tesseract and OCR data download externally. Resource budgets apply and there is no autosave.
References: PDF.js · Tesseract.js
Import a supported PDF, inspect extracted text and OCR regions, then arrange text, tables and figures into an editable reconstruction. The tool estimates layout and leaves room for manual review rather than promising a pixel-identical conversion.
Authored example: Reconstruct a one-page report with a heading, two paragraphs, a small table and a logo. Check reading order and table cell content individually before comparing the reflowed DOCX with the source.
Limits and processing: PDF.js and Tesseract.js plus OCR data download from external CDNs. Text/table regions are heuristic; manual figures need review. DOCX reflows and does not preserve exact source positions; positioned HTML depends on fonts and browser rendering. Projects are not autosaved.
No. DOCX output reflows in the target editor and does not preserve exact source positions.
No. Detection is heuristic and figures are manual; review the reconstructed content before relying on it.