Most online converters upload your file to a server, convert it there and send the result back. Krawly's converters skip the round trip: the conversion code itself is loaded into your browser, so the file is read and processed on your own device.
Images are decoded by your browser and re-encoded with its built-in canvas encoder; iPhone HEIC photos use libheif compiled to WebAssembly. PDF pages are rendered with PDF.js, the PDF engine behind Firefox's viewer, and edited with pdf-lib. Text recognition uses Tesseract, the open-source OCR engine, also compiled to WebAssembly.
Because nothing is uploaded, contracts, ID scans, invoices and personal photos stay private, and large batches are not slowed down by your upload speed.
Are my files uploaded to a server?
+
No. Every converter on this page runs inside your browser with JavaScript and WebAssembly. The file is read from your device, converted in memory and handed back as a download. Nothing is sent to Krawly, so there is nothing to store or delete afterwards.
Is there a limit on how many files I can convert?
+
There is no daily limit and no account needed. Image converters take up to 50 files per run (OCR takes 20), and you can start another run straight away. Individual files can be up to 50 MB for images and 200 MB for PDFs.
Do the converters add a watermark?
+
No. The output is exactly the converted file — no watermark, no added pages and no branding.
Why is the first OCR run slower than the next ones?
+
Text recognition needs the Tesseract engine and a language model, a few megabytes per language. They download the first time you use OCR and are then cached by your browser, so later runs start almost immediately.
Which browsers are supported?
+
Current versions of Chrome, Edge, Firefox and Safari on desktop and mobile. Conversion speed depends on your device, and very large images or long PDFs are handled more comfortably on a computer than on a phone.