About Toolkitbar
Toolkitbar is a set of free media tools that run inside your browser. Nothing you open here is uploaded, queued or stored: the processing happens on your own device, and the file never leaves it.
That one decision shapes everything else on the site — what it can do, what it cannot, and why it does not need your email address.
How it works
Most online media tools are a thin front end over a server. You upload, the server converts, you download the result. That model requires paying for bandwidth, storage and CPU per file, which is why those sites need size caps, queues, accounts, watermarks and ads.
These tools invert that. Video is processed by a WebAssembly build of FFmpeg loaded into the page; images use the JPEG, PNG and WebP codecs your browser already contains. Both run on your hardware. The server's only job is to send the page, which is why it can be free without a catch.
You can verify the claim rather than take it on faith: open your browser's network panel while converting, or simply disconnect from the internet once the page has loaded. The tools keep working.
What this costs you
Honesty about the trade-off matters more than the pitch. Browser-based video encoding is several times slower than a native desktop application, because it runs single-threaded inside a sandbox. A long or high-resolution video will take a while.
The video tools also download a one-off encoder of roughly 31 MB the first time you use one in a session. Your browser caches it afterwards, but the first conversion carries that wait. The image tools download nothing at all and finish in milliseconds.
File size is limited by your device's memory rather than by a policy. Around 500 MB of video is comfortable on a typical laptop; a phone handles considerably less, and a very large file may simply fail where a desktop would succeed.
What is not supported
The image tools read only what your browser can decode — JPEG, PNG, WebP, GIF and BMP. Apple's HEIC and camera raw formats such as CR2, NEF and ARW cannot be opened, because no browser decodes them without an additional library.
HEVC / H.265 video support is limited in the encoder build used here. If an iPhone recording fails to convert, re-exporting it from Photos with the "Most Compatible" setting produces H.264, which works.
Re-encoding an image through a canvas drops its EXIF metadata entirely. That removes GPS coordinates, camera model and timestamps — usually welcome before publishing a photo, but worth knowing if you are archiving one.
Privacy
No file you process is uploaded, so there is nothing on a server to leak, subpoena or forget to delete. There are no accounts, so there is no password to breach.
The "recently used" list on the home page is stored in your browser's local storage and holds only tool names — never a file name, size or anything derived from a file. It never leaves your device, and the Clear button removes it.
One thing does reach a third party, and it should be said plainly: the site is funded by Google AdSense, which loads a script from Google and may set cookies to measure and personalise advertising. That is separate from your files, which Google never sees — but it does mean the site is not free of third-party tracking. The privacy policy sets out what this covers and how to opt out.