File Formats & Media

File Conversion

Definition

Converting a file means reading its structure with something that understands the source format and writing an equivalent with something that understands the target. Some conversions lose nothing: a PNG rewritten as a lossless WebP holds the same pixels, and a CSV read into a spreadsheet and written back out is the same table. Most lose something. A DOCX exported to PDF gives up its editability and the ability to reflow; a JPEG re-saved as another JPEG is re-encoded and loses a little more detail each time, which is why repeated round trips visibly degrade an image. A third category is not conversion at all but reconstruction — pulling text out of a scanned PDF needs OCR, which is a recognition step that can be wrong, not a format translation that cannot.

Why It Matters

The reason this matters on a hosting page is blunt: a static host does not convert anything. 99helpers serves the exact bytes you upload with the type that matches the extension, and it will not turn your .docx into a web page, resize a 6,000-pixel photograph, or make a PDF out of your slides. Anyone who expects otherwise publishes a link that downloads a 46 MB deck to a phone. Doing the conversion first is usually the whole optimisation: a hero image converted from a 2.4 MB JPEG to a 380 KB WebP cuts about two seconds off a page load on a typical mobile connection, and an exported PDF turns a deck that needed an application into something that opens in the browser on the first tap.

How It Works

The practical tools are small in number and worth knowing by name. ImageMagick and the cwebp and avifenc encoders handle images from the command line; Squoosh does the same job in a browser tab with a visual quality slider. LibreOffice converts Office documents headlessly with soffice --headless --convert-to pdf, which is what most server-side converters wrap. Pandoc turns Markdown, DOCX, HTML and a dozen others into each other. FFmpeg handles audio and video, including the MP4 to WebM route. Each of these runs on your machine or in your build, produces a finished file, and that file is what gets uploaded. Where a conversion has to happen after publication — a user uploading a photo that needs a thumbnail, say — you need an image service or a function, not a static host.

Real-World Example

A designer has a 32-slide deck and a folder of 18 photographs at full camera resolution, 61 MB in total. Before uploading they export the deck to PDF at 2.8 MB and batch-convert the photographs to WebP at 85 per cent quality, which brings the folder to 3.1 MB. The whole site goes onto 99helpers as one drag-and-drop and loads at portfolio-2026.99helpers.site in under two seconds on a phone. Had the originals gone up untouched, the same visitor would have waited through 61 MB, and the analytics would have shown the bounce rate that goes with it.

Common Mistakes

  • Expecting the host to convert on the fly — a static file service returns the bytes it was given, so the .docx you uploaded is the .docx a visitor downloads
  • Re-encoding a lossy file repeatedly — each JPEG-to-JPEG round trip adds compression artefacts that no later step can remove
  • Converting a scanned PDF and wondering where the text went — there was never any text, only an image of one, and extracting it requires OCR
  • Uploading a file to an unknown web converter because it was quick — a contract or an ID document goes to a third party you have not checked, with whatever retention policy they happen to have

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →