Runs on your device
Compress, convert, trim and resize video and images entirely inside your browser. No upload, no watermark, no account, no file size limit.
The page opens your file and processes it on your own hardware. Check the browser's network panel, or disconnect after the page loads — the tools keep working either way.
No sign-up, no email, no logo stamped into the corner of a free-tier export, and no daily cap. There are no per-file server costs to recover.
Images finish in milliseconds. Video runs at your machine's speed rather than a shared server's, so a busy evening never slows you down.
These video tools run entirely inside the web browser using a WebAssembly build of FFmpeg. Because the processing is local, files are never uploaded to a server, there is no file size limit imposed by the service, no account is required, and no watermark is added to the output.
Make a video file smaller without a visible drop in quality.
Extract the soundtrack from a video as a plain MP3 file.
Turn a few seconds of video into a shareable animated GIF.
Keep only the section of a video you actually need.
Change a video's resolution or reshape it for a specific platform.
Remove the sound from a video without re-encoding the picture.
Fix a video that was recorded sideways or upside down.
Convert iPhone and QuickTime MOV files into universally playable MP4.
Convert web-native WebM files into MP4 that editors and phones accept.
Modernise legacy AVI files into smaller, widely supported MP4.
Convert MKV to MP4 — usually instantly, and without quality loss.
Convert video to WebM for smaller, faster-loading web pages.
These image tools run entirely inside the web browser, using the JPEG, PNG and WebP codecs the browser already ships. Because the work is local, images are never uploaded, a typical photo is processed in well under a second, there is no file size limit imposed by the service, no account is required, and no watermark is added.
Make an image file smaller without a visible drop in quality.
Scale an image down to an exact pixel width.
Turn a sideways photo upright, or mirror it.
Turn a heavy PNG into a far smaller JPG.
Convert a JPG into a lossless PNG.
Turn a WebP saved from the web into a universally accepted JPG.
Convert WebP to PNG and keep the transparent background.
Convert images to WebP for far smaller files and faster pages.
Pick a tool
Choose from the video and image tools above. Each one does a single job, with sensible defaults already selected.
Add your file
Drag it onto the box or click to browse. It stays on your device the whole time.
Download the result
Save the output. The original file is never modified.
Toolkitbar is a collection of free media tools that run inside the web browser instead of on a server. Video is handled by a WebAssembly build of FFmpeg and images by the browser's own JPEG, PNG and WebP codecs, both executing on the visitor's own device. Because nothing is uploaded, there is no queue, no size limit imposed by the service, no account requirement and no watermark on the output.
Yes. There is no paid tier, no watermark, no daily limit and no account. The processing runs on your device, so there are no server costs to recover per file.
No. Every tool reads the file into the page and processes it locally. You can verify this by opening your browser's network panel, or by disconnecting from the internet after the page has loaded — the tools keep working.
There is no limit imposed by the service. The constraint is your device memory. Images are comfortable even at 50 megapixels; video up to roughly 500 MB is fine on a typical laptop, and phones handle less.
No. Everything runs in the browser tab. The video tools download a one-off encoder the first time you use them, which the browser then caches; the image tools download nothing at all.
Any current version of Chrome, Edge, Firefox or Safari, on desktop or mobile. The video tools additionally need WebAssembly and web workers, which all of those provide.
Yes, though memory is tighter. Image tools are quick on any modern phone. Large video files may fail where a laptop would succeed — that is a hardware limit, not a policy one.
