Frequently Asked Questions & Support

Absolutely. FileMorph operates entirely client-side (in your browser). Your files are processed directly by your device using HTML5 Web APIs — we don't have backend servers, databases, or cloud storage. Close the tab, and the data is gone.

No. There is no upload step in FileMorph's code — your file is only ever read into your browser's local memory, converted there, and then handed back to you as a download. We have nothing to store because nothing is ever sent to us. Standard, privacy-respecting web analytics may record anonymous page visits, but never file contents.

Mostly. The page itself and its small helper libraries load from a CDN the first time you visit. After that first load, the actual conversion work needs no network connection at all — only re-opening the page in a browser tab that hasn't cached the libraries yet would require you to be back online.

Yes. FileMorph reads the text layer out of your PDF and rebuilds it as an editable .docx file, no account or paywall involved. Because this happens client-side, it works on the text content of the document — complex original layouts, tables, and images from the PDF are not reproduced pixel-for-pixel, just the text.

Yes to both. The Converter tab extracts text from PDFs, and it can also render each page of a PDF as a JPG or PNG image. If your PDF has more than one page, the rendered images are bundled into a single .zip so you get everything in one download.

FileMorph reads the raw text out of your .docx file and lays it out into a fresh PDF. As with PDF to Word, this is a text-based conversion — rich formatting like custom fonts, embedded images, and complex tables in the original Word file won't carry over.

The old binary .doc format (pre-2007 Word) needs a much heavier parser than a browser can reasonably run. If you have a .doc file, open it in Word, Google Docs, or LibreOffice and use "Save As → Word Document (.docx)" first — then FileMorph can take it from there.

iPhones save photos in High-Efficiency Image Container (HEIC) format, which many Windows PCs and websites can't read. Go to the Converter tab, drop your HEIC photo in, choose JPG as the output, and click Morph Files Now. Decoding happens locally in your browser.

You can convert freely between JPG, PNG, WEBP, GIF, BMP, TIFF, HEIC/HEIF and SVG. Browsers can decode JPG, PNG, WEBP, GIF, BMP, SVG and HEIC (via a small decoder library) as a starting file, but they can't reliably decode TIFF — so TIFF only works as an output format, not an input one. If you need to start from a TIFF, re-save it as PNG first using desktop software, then upload the PNG.

Turning a photo into a true hand-drawn vector isn't something a browser can do automatically. When you choose SVG as a target for a raster image, FileMorph embeds your image inside a valid .svg container so it can be placed in layouts that require an SVG file. It won't gain new vector paths or become editable as shapes — it's your original picture inside a resizable wrapper.

The compressor uses the HTML5 Canvas API. When you upload an image, we draw it onto an invisible canvas and re-export it at the quality level you choose with the slider — JPG and WEBP support adjustable quality; PNG stays lossless so the slider doesn't apply to it. This is how we shrink JPG or compress PNG files instantly without a server.

Yes. On the Converter page you can drop or select multiple files at once. Each one converts and downloads individually, and you can watch the status of every file update live in the list.

There's no artificial limit set by FileMorph, but because everything runs in your browser's memory, very large files (for example, an extremely long PDF or a huge uncompressed image) are limited by your device's own available RAM rather than by us.

Sure — head to the homepage footer and click "Show tutorial again", or click here.