Known limitations

File size and memory

Files are processed in browser memory. Extremely large files (hundreds of pages or hundreds of megabytes) may be slow or fail on lower-end devices. There is no server queue to offload to — which is also why files stay private.

OCR accuracy

OCR quality depends on the source scan: low resolution, skew, noise, unusual fonts and mixed layouts reduce accuracy. OCR never reads a document perfectly, and its output should be reviewed.

Complex PDF structures

• Password-protected PDFs must be unlocked before other tools can process them.
• Corrupted PDFs may fail to parse.
• Heavily compressed or unusual fonts can make in-place text editing or extraction unreliable.
• Some forms, annotations and interactive elements are preserved only partially by conversion tools.

What this means for you

Keep original copies of important documents, review processed output before relying on it, and contact us if a tool fails on a file you expected to work.

Browser limitations

Processing happens inside the browser tab, which means the tools are limited by what browsers allow: memory per tab, available CPU, and how long a script may run before the browser asks for confirmation. On a phone or a lower-end laptop, large documents are slower and more likely to hit those limits than on a desktop with more memory.

File types that are not supported

Some formats are intentionally not supported. For example, we do not claim to handle every proprietary or legacy format, and heavily encrypted or DRM-protected documents cannot be processed. If a tool rejects a file, it explains why rather than silently producing garbage.

How limits are communicated

Each tool page lists its own limitations and a direct answer about what the tool can and cannot do. If processing fails, the error message explains the cause and what to try next, so you are never left guessing.