Limits

Current limits by tool family

Limits protect reliability, browser memory, server cost, and user experience. If a tool rejects a file, the safest next step is usually to inspect the file type, size, page count, or format before retrying.

Details

What to know

1

Browser memory limits

Browser-local tools depend on your device memory and the browser's file APIs. Large images, huge archives, large XLSX files, and multi-hundred-page PDFs may fail locally even when the file is valid. Split, compress, or inspect the file before retrying.

2

Temporary job limits

Server-backed PDF, Office, OCR, HEIC, and HTML conversion jobs require a signed-in paid account and use conservative file-size, page-count, timeout, output-count, and output-byte limits. Browser-local tools remain available without signing in.

3

Format support is intentionally narrow

A live tool supports the formats listed on its page. Similar-looking formats can behave differently, such as DOCX versus older DOC, digital PDFs versus scanned PDFs, JPG versus HEIC, or simple XLSX worksheets versus complex workbooks.

4

When a limit blocks a task

Use inspection tools first: check file type, file size, PDF page count, PDF text layer, CSV delimiter, image dimensions, archive contents, or Office layout risk. Then choose a smaller or safer workflow.

Related tools