How AnyFileConvertor works

Conversion that happens on your own device, in a browser tab, with no upload step. Here is the whole pipeline, including the parts that are still being built.

  1. 1

    Drop the file

    Drag a file onto the drop area or press the browse button. The tool reads the file locally and shows its name, size and detected type.

  2. 2

    Confirm the operation

    Check the input format the tool detected and pick the output format. Options that change the result, such as quality or page range, are shown here.

  3. 3

    Process locally

    The engine is downloaded only for the tool you opened, then runs in a Web Worker so the interface stays responsive while progress is reported.

  4. 4

    Download the result

    The finished file is offered for download straight from browser memory. Reset the tool to clear it and start again.

The pipeline, stage by stage

Every stage after the initial page load happens on your machine. This is the contract the architecture is built around.

  1. File Your device Selected through the browser File API. No upload.
  2. Validate Your device Extension, declared MIME type and size are checked first.
  3. Engine Web Worker The matching engine module is fetched, then runs off the main thread.
  4. Result Blob URL Output is assembled in memory and offered as a download.
  5. Cleanup Your device Buffers are released and object URLs revoked.

Engine status

In progress
Category Engine Processing Status
Images Browser codecs + WebAssembly for HEIC/AVIF Runs locally In progress
PDF PDF toolkit in a Web Worker Runs locally Planned
Documents Document layout engine Runs locally Planned
Audio & Video FFmpeg compiled to WebAssembly Runs locally Planned
Data Plain text codecs Runs locally Planned
Archives DecompressionStream + WebAssembly Runs locally Planned
CAD & 3D Geometry engine Runs locally Planned
Scientific Binary array readers Runs locally Planned

Engines are implemented in the order that gives the most people a working converter first: images, then PDF and documents, then media.

Under the hood

  • File API and Blob URLs for local reads and downloads
  • Web Workers so the interface never freezes
  • WebAssembly for codecs browsers do not ship
  • Streams and ArrayBuffer for large files
  • No file upload endpoint exists on the server

Questions about the process

Why do some tools need a download before converting?

Formats such as HEIC, MKV or DOCX need a codec the browser does not include. Those tools fetch a compiled WebAssembly module the first time you use them, and the browser caches it afterwards.

What happens if my browser is unsupported?

The tool checks for the features it needs before starting. If something is missing you get a clear explanation instead of a failed conversion, rather than a broken progress bar.

Why is nothing uploaded even for large files?

The file is turned into a binary buffer inside the page, processed by a worker and reassembled as a download. Bytes never cross the network.

Try it with a file you already have

All 240 tools are connected and convert immediately in your browser.

Browse all tools Read the guides