HOW CONVERSION WORKS

From upload to download

Every conversion follows the same short workflow. The converter only offers routes that are both supported by an installed engine and enabled on this server.

1. Choose a file and an output format

Select a document or spreadsheet from your device. The upload is limited to 25 MB and one file per request. The output choices are read from the server, so you will only see formats that can actually be produced for your input type.

2. The file is checked before conversion

The server checks the extension, the detected file type, the file signature, and the container structure. Office files must contain the expected document part, PDF files must start with a PDF header, and compressed containers are checked for unreasonable expansion. A file that does not match its extension is rejected before any conversion tool runs.

3. Conversion runs in the background

The upload response returns a private token. A queue worker picks up the job, copies the source into a private temporary directory, runs the local conversion tool with a time limit, and checks that the result is a valid file of the requested type. The browser polls the status endpoint until the job is complete or fails.

4. Download, expiry, and cleanup

A completed file is available through a temporary link for 1 hour(s). Source files are deleted after processing. Expired results and stale job records are removed automatically by the scheduled cleanup command. You can also delete a job and its files from the result flow or from the admin dashboard.

Why a job can stay on “queued”

The worker runs on a schedule, so a new job may wait up to about one minute before it starts. Once processing begins, the status changes to “processing”. Large files and complex layouts take longer. Keep the result page open: the download token is held by that page, and refreshing can lose access to the result.

What can change during conversion

Different formats store layout, fonts, formulas, and images in different ways. Complex tables, embedded objects, unusual fonts, and page breaks may move or change. Macro-enabled files are never executed, and macros may be removed. Always review the converted file before relying on it.

If a conversion fails

The source file may be damaged, password-protected, too complex, or missing a feature supported by both formats. Try a simpler file or a different output format. The FAQ lists common causes, and the contact page accepts a report with the input format, output format, file size, and the safe error message shown on screen.