Disclaimer
Important limitations of the browser-based tools on Ajee Convert, including format support, accuracy of measurements and the absence of any guarantee about results.
This page sets out what the tools on Ajee Convert can and cannot do, so that nothing about their behaviour comes as a surprise. It is worth reading before you rely on a conversion for anything important.
Browser engine dependency
All processing uses the audio, canvas, font and WebAssembly capabilities of your browser. Different browsers decode different formats and support different output codecs. A conversion that succeeds in one browser may fail in another, or produce a slightly different file. If a tool reports an error, trying a current version of Chrome, Edge or Firefox is the first thing to attempt.
Video conversion
Video tools use FFmpeg compiled to WebAssembly running on a single thread, so no special server headers are required. The trade-off is speed: expect roughly real time or a little faster on a modern laptop, and considerably longer on older hardware or for long files.
Lossy formats and generations
Re-encoding a lossy format adds a further generation of compression. Converting a 128 kbps MP3 to 320 kbps does not restore the detail the original encoder discarded — it produces a larger file carrying the same artefacts plus a fresh set. No tool on this site claims otherwise.
Genuine browser limitations
The following operations cannot be performed in a browser and are labelled as limited rather than offered as working tools: identifying a typeface from an image, converting TrueType outlines to PostScript ones or back, producing or expanding WOFF2 files, extracting subtitle tracks from a video container, and reading a video's frame rate. Each of those pages explains the limitation and the desktop route that works.
Measurements and estimates
Sample rates, bitrates, channel counts, peak and RMS levels, dimensions and durations reported by the tools are measured from the actual decoded media and are as accurate as the underlying browser APIs allow. Calculator results are arithmetic models and are close approximations rather than guarantees — real encoders are affected by content complexity, container overhead and metadata.
File-size expectations
Compression does not always reduce file size. Converting a photographic JPEG to PNG, re-encoding an already-efficient file at a very high quality setting, or transcoding an efficient codec to a less efficient one commonly produces a larger file. The tools report the real before-and-after sizes so you can see when this happens.
No professional advice
Nothing on this site constitutes legal, licensing, broadcast-engineering or archival advice. Font embedding rights, music licensing and delivery specifications are matters on which you should consult the relevant licence terms or a qualified professional.
Always keep your originals
This site only reads your files and never modifies them. Even so, keep an untouched original of anything important. Verify every output before deleting a source file or relying on a conversion for a delivery deadline.