File format support: PDF, images, CSV, EPUB and media
Choose a supported format and understand byte, pixel, page and decoded-memory limits before converting. Includes when a desktop workflow is more suitable.
Images: JPEG, PNG and WebP
For photos, compare JPEG and WebP quality and size. Choose PNG or transparency-capable WebP for a transparent background. Images are limited to 20 MiB each, 80 MiB per batch, 20 files and 16 million decoded pixels. GIF, HEIC and RAW are not supported by the general image converters.
PDF: page operations and text extraction
PDFs are limited to 30 MiB each, 80 MiB total and 300 pages. Merge, reorder and page numbering suit finished documents. Cropping only changes the visible area and is not secure redaction. Text extraction does not OCR image-only scans.
Data: CSV, TSV, JSON and NDJSON
CSV/TSV are delimited text, not multi-sheet workbooks with calculated formulas. JSON supports nested data; NDJSON stores one record per line. Pasted text is limited to 1 MiB; CSV files to 10 MiB and 200,000 cells. Confirm UTF-8, delimiters and headers before conversion.
Documents: TXT, Markdown, DOCX and EPUB
TXT requires the correct encoding. Markdown stores lightweight structure; DOCX and EPUB contain internal files. Imports check expanded sizes and entry counts and do not handle password-protected documents. Pagination, fonts and complex tables can vary by reader; inspect output in its destination app.
Archives and media
ZIP packages several files; GZIP compresses one data stream. Neither implies encryption. Archive input is limited to 50 MiB; extraction also checks expanded size and compression ratio. Media processing depends on browser codecs. Desktop tools are better suited to large files.
Choose by the information you need to preserve
Size on disk is only one resource measure. A compressed image can expand to millions of pixels, and an archive can contain much more data than its download size suggests. A file below the byte limit can still exceed pixel, page or expanded-size limits.
When you need tracked changes, interactive PDF forms, sophisticated publication layout or large media batches, a focused browser conversion may not preserve everything. Keep the source and use a workflow that supports those features instead of accepting a visually plausible but incomplete export.
| Need to retain | Consider | Watch for |
|---|---|---|
| Transparency | PNG or WebP | JPEG fills transparent areas |
| Editable document structure | DOCX | Complex layout may change |
| Chapter navigation | EPUB | Actual links and reading order |
| Nested records | JSON | CSV cannot express all nested structures |
| Multiple packaged files | ZIP | GZIP is one compressed stream |
Before you finish
- Check the per-tool limits displayed above the workbench.
- Use a small representative file before a full batch.
- Reopen the export in the app that will consume it.
- Never rename an unsupported extension as a substitute for conversion.