Frequently Asked Questions
Straight answers to the questions people ask most about Convert.rest — privacy, formats, limits and troubleshooting. If your question is not here, the contact page gets you a human reply.
No. Every conversion and tool on Convert.rest runs entirely in your browser using JavaScript and WebAssembly. Your files stay on your device and are never sent to, stored on, or analysed by a server.
Word to PDF accepts DOC, DOCX, RTF and ODT. PDF to Word converts text-based PDFs to editable DOCX. The Base64 tools accept text, and the image tools handle PNG, JPEG, WebP, GIF, BMP, AVIF and SVG. Old binary .doc files should be saved as .docx first.
The Word↔PDF converters accept files up to 50 MB per file and up to 20 files per batch. The image tools accept files up to 10 MB, and decoded Base64 output is capped at 15 MB to keep the tab responsive.
Yes. Batch mode accepts up to 20 Word or PDF files at once, converts them one after another in your browser, and lets you download each result individually or bundle everything into a single ZIP archive.
PDF to Word works with text-based PDFs — files where you can select and copy text. Scanned, image-only PDFs do not produce editable text without OCR, and OCR is not available yet; it is on the roadmap.
No. Base64 is an encoding, not an encryption. It represents bytes as printable ASCII characters so they can travel in text, URLs or data. Anyone who receives Base64 can decode it back to the original bytes with the Decode tool — never treat Base64 as a way to keep data secret.
A single failed file is skipped without affecting the rest of the batch. Failures are almost always one of the classic cases: a password-protected document or an old binary .doc. Save the file as .docx and try again. If it still fails, use the Report a problem page.
Current versions of Chrome, Firefox, Safari and Edge on desktop and mobile. The converters require WebAssembly, which every modern browser provides. For very large files on low-end phones, processing simply takes longer.