HD screenshot
- Input
- 1280x720 px
- Expected output
- 1.25x -> 1600x900 px
Enlarged until the long side reaches 1,600 px.
copy text from image
To lift the text from a screenshot, copy the screen area, paste it here with Ctrl+V, pick the language and click extract. The text shows up below, ready to copy or download as .txt.
Enlarged until the long side reaches 1,600 px.
The smaller the image, the bigger the enlargement, up to the 3x cap.
Hit the 3x cap: images this small lose letters under any engine.
Already over 1,600 px, so it is not enlarged.
Only the first time; afterwards it stays cached in the browser.
No. Recognition happens in your browser via WebAssembly; the image never leaves your device. Only the OCR engine and the chosen language files are downloaded from a CDN on the first run, and they are cached afterwards.
No. Recognition runs in your browser through WebAssembly. Only the engine and the language data are downloaded from a CDN the first time.
Very poorly. The OCR is optimized for printed or digital text, and handwriting gives unpredictable results. For handwritten notes, typing is still the safest route.
Yes. They run in sequence on the same engine, each with its own text, and an option merges everything into one document with each file name as a heading.
On the first run the browser downloads the language data (~11 MB in total) from a CDN. After that it is cached.
Use “Sparse/Code” for plates, serial numbers, codes or short strings that are not sentences (like Morse code). In Automatic mode the tool already tries that mode on its own when the first result has low confidence.
Recognition runs entirely in your browser (WebAssembly). The image is never sent to a server; only the OCR engine and language files are downloaded from a CDN on the first run.