About Amon Flux

Who publishes this

Amon Flux is built and maintained by Marco Caturano, an independent software developer based in Livorno, Italy. It is not a company and there is no team behind it. Every tool, every guide and every line of the interface is the work of one person, which is worth stating plainly so you know what you are relying on.

The site is funded by advertising, shown only to visitors who opt in. There are no paid placements in the guides, no affiliate links, and no sponsored recommendations. When a guide says a format or setting is the right choice, that is the conclusion, not a promotion.

Corrections are welcome. If something in a guide is wrong or out of date, write to info@amonfluxconverter.com and it will be fixed and the revision date updated.

Why it works this way

Most online converters follow the same pattern: you upload a file, a server processes it, and you download the result. That works, but it means handing a copy of your document to an operator you know nothing about, waiting for it to travel in both directions, and trusting that it is deleted afterwards.

Browsers have been capable of doing this work themselves for several years. WebAssembly lets compiled libraries such as FFmpeg run at close to native speed inside a tab, and the File API gives a page direct access to files you choose without sending them anywhere. Amon Flux is built on that, so processing happens on your own machine.

What the approach costs

It is only honest to state the limits alongside the benefits.

• Speed depends entirely on your hardware. Video encoding in particular is much slower than a dedicated server would manage, and an older laptop will feel it.
• A browser tab has a memory ceiling. Very large video files can exhaust it, and the tab may become unresponsive or reload. Desktop software has no such constraint.
• Some features require the browser to enable shared memory, which needs specific security headers. Where a browser or a corporate configuration blocks this, the media tools degrade to a slower single-threaded path or do not run at all.
• There is no cloud storage or account, so nothing is saved between sessions. Close the tab and the work in progress is gone.

What is built on

The interface is React with Tailwind CSS. Image conversion uses the browser's own canvas encoders. PDF assembly and merging use pdf-lib and pdf.js. Vector tracing uses imagetracer. Audio and video conversion use a WebAssembly build of FFmpeg. These are open source projects maintained by other people and the work here is the interface around them, not the codecs themselves.

If you want to understand the reasoning behind the settings these tools expose, the guides go through them in detail.