About ToolsAllInOne

What this is

ToolsAllInOne is 245 tools — file conversion and editing, PDF, image, video and audio utilities, developer tools and calculators — all running directly inside your web browser. Most online converters ask you to upload a file, process it on their servers, and hand back a download link. This one does not. The conversion engines run as WebAssembly on your own machine, so the file never leaves your device.

Why it works that way

Uploading a file means trusting a stranger with it. For a holiday photo that may not matter much; for a signed contract, a medical scan, a passport copy or an internal spreadsheet, it matters a great deal. Running the conversion locally removes the question entirely — there is no server copy to leak, subpoena, retain or sell, because no copy is ever made.

It also removes the commercial limits. There is no upload queue, no daily quota, no watermark and no paid tier, because the cost of converting your file is paid by your own CPU rather than by our hosting bill. What it does not remove is physics: your browser has a memory ceiling, and that puts a real limit on very large video files. Those limits are set out below.

What it uses

• Images — the browser's own canvas and image decoders.
• Audio and video — ffmpeg, compiled to WebAssembly. It is the same engine many desktop converters are built on. It is around 32 MB and is downloaded once, on your first audio or video conversion, then cached by your browser.
• PDF — pdf-lib for building PDFs and pdf.js (Mozilla) for rendering them to images.
• Data formats — js-yaml and marked, plus straightforward parsing code for CSV and Base64.
• OCR — Tesseract.js and its English recognition data.
• On-device AI tools — ONNX Runtime (background removal), MediaPipe (face blur) and Transformers.js (transcription, automatic subtitles, translation, text-to-speech and AI upscaling).

These libraries are all open source.

Most of the code this site uses is served from this site itself, including the Transformers.js library, the OCR engine with its English language data, the face-detection engine and model, the background-removal model and the text-to-speech voice. A few large engines and models are fetched from public CDNs the first time you use a tool that needs them, and are then kept on your device:

• jsDelivr, with unpkg as a backup: the ffmpeg audio and video engine (about 32 MB).
• jsDelivr: the WebAssembly runtimes used by the AI tools and the ONNX runtime used by background removal.
• Hugging Face: the machine-learning models for transcription and automatic subtitles (Whisper), translation (Opus-MT), text-to-speech (SpeechT5) and AI upscaling (Swin2SR).

Fetching them from public CDNs is what keeps the site free to host. When one of those downloads happens, the provider sees your IP address and browser user-agent, as it would for any file it serves; the privacy page covers this. The files you convert are never part of that request. Every library and its licence is listed on the open-source page.

Limits, and what they cost you

Running everything on your own device has real trade-offs. We would rather state them plainly than let you discover them halfway through a long conversion.

There is a hard 2 GB ceiling on audio and video

The media engine runs in WebAssembly, which can address at most 2 GB of memory — that is a limit of the technology, not of your computer, so a machine with 64 GB of RAM does not raise it. That 2 GB has to hold your input file, the finished output and the encoder's working memory all at once. In practice files beyond roughly 900 MB cannot complete, and the site says so before you start rather than failing partway through.

Conversion is single-threaded, so it is slow

The engine uses one CPU core. On a desktop expect video to take somewhere around as long as the clip itself; on an older phone it can be ten to twenty times longer. Audio, images, PDFs and data files are quick — it is video specifically that is demanding.

It will use your battery and make the device warm

A long video conversion holds one core at full load for the whole duration. On a laptop or phone that means noticeable battery drain and heat. It will not damage anything — your operating system throttles the CPU long before that becomes possible — but it is not something to start on 5% battery.

The tab has to stay open

All the work and the finished file live in the page. Closing the tab, or letting a phone suspend it, loses the conversion. The page warns you if you try to leave while a conversion is running.

Other limits we apply deliberately

• Animated GIF covers the first 30 seconds of a clip. GIF barely compresses across frames, so an uncapped conversion produces enormous files and can exhaust memory.
• PDFs are handled up to 100 pages at a time, and each page is rendered within a bounded pixel budget, so a single oversized page cannot blow up on its own. A long document is still heavy work.
• Very large images are limited by your browser's maximum canvas size, which is much smaller on iPhones and iPads than on a desktop.

Data use on first use

The media engine is about 32 MB and is downloaded once, the first time you convert audio or video. The OCR and on-device AI tools each download their own engine or model the first time you use them. These range from about 10 MB (face blur) to about 215 MB (text-to-speech), and each tool's page gives its own figure. Your browser then caches them. If you are on a metered connection, that is worth knowing before you start.

It needs a connection the first time

The work itself is local, but each page and each engine has to be fetched over the network once before it can be cached. After that, a page you have visited and an engine served from this site, or the audio and video engine once used, will work offline. The AI tools are the exception: parts of their engines come from public CDNs and are kept only by your browser's ordinary cache, so they may need a connection again. A tool you have never opened, or an engine you have never run, always needs a connection the first time.

Who runs ToolsAllInOne

ToolsAllInOne is built and run by ToolsAllInOne. It launched in 2026. Full operator details are in the legal notice.

Contact

Questions, bug reports or takedown requests: contact@toolsallinone.com