Local processing
Supported prepare, compress, convert, and merge work runs in your browser. Timamu does not upload that source media to a processing server.
Supported Timamu Web prepare, compress, convert, and merge tools run in your browser. Timamu does not upload source media to a Timamu processing server for those workflows. Your originals stay intact, Timamu writes a separate prepared output, and it checks completed outputs before marking them ready.
Supported prepare, compress, convert, and merge work runs in your browser. Timamu does not upload that source media to a processing server.
Timamu writes a separate prepared output. Routine preparation leaves your original intact.
Re-download, retry, or remove recent work only while its local output remains on that device and browser. Timamu does not store that media.
Invalid or incomplete outputs are not silently presented as ready.
Timamu attempts recovery only when it can do so within clear limits.
File size and savings come from the actual result, not an estimate.
Some file damage is irreversible. Timamu attempts recovery only for supported file types and conditions. Web history can download, remove, or retry a finished job while that local output remains available. Stronger native recovery ships with Desktop and is not a public download today.
If you discover a security issue or a repeatable output problem, contact the Timamu team with the version, platform, and steps to reproduce. Include a sample only if you choose to, and keep it non-sensitive. Timamu does not keep a customer media library of files you prepare.
Contact the Timamu team for security-sensitive or file-integrity reports.
Make it smaller, fit a size limit, convert it to a usable format or prepare it for where it needs to go — directly in your browser for supported Web jobs.