Images
- JPG
- PNG
- WEBP
- TIFF
- HEIC
mozjpeg, libwebp and oxipng. iPhone HEIC and TIFF are decoded and rewritten as JPG or WebP.
Processing happens 100% on your device. Your data never leaves your computer.
Drag your files here
The output will never exceed this size.
One file is processed per run.
No document or data is ever stored on external servers. The entire process runs locally and privately in your own browser. Your confidential, legal or tax files never leave your machine.
The same engine, set up for whatever you need to shrink.
mozjpeg, libwebp and oxipng. iPhone HEIC and TIFF are decoded and rewritten as JPG or WebP.
A lossless rewrite first, keeping text selectable. If that is not enough, controlled rasterisation.
ffmpeg.wasm. For long clips the bitrate is calibrated on a segment, then the full encode runs.
DOCX, PPTX, XLSX and ZIP: the package is opened, inner images shrunk, and it is sealed again.
Your files travel across the internet, land on third-party servers and are exposed to security risks.
The file is dropped and processed directly on your computer. Zero servers, zero risk to your data.
Filely is a free web tool that compresses files down to a maximum size in megabytes chosen by the user. It runs entirely inside the browser using WebAssembly: the file is never uploaded to a server, no sign-up is required, and the processing happens on the user's own machine. It handles JPG, PNG, WEBP, TIFF and HEIC images, PDF documents, MP4 and MOV video, MP3 and WAV audio, animated GIF, and DOCX, PPTX, XLSX and ZIP packages.
| Aspect | Filely (in your browser) | Cloud compressor |
|---|---|---|
| Where the file is processed | On your own machine | On someone else's server |
| File upload | None | Required, and you wait for it |
| Copy held by a third party | Never created | Yes, under their policy |
| Works offline | Yes, once loaded | No |
| Sign-up or account | Not needed | Usually, to lift limits |
| What sets the speed | Your processor and memory | Your connection and server load |
Most compressors give you a quality slider and let you guess how heavy the result will be. Filely works the other way round: you set the ceiling in megabytes and the app searches for the setting that keeps the most quality without going over it.
It helps in any situation where the destination imposes a maximum weight: a form that rejects the attachment, an email that will not send, a page that loads slowly or a shared folder running out of room. Instead of exporting again and again by eye, you set the number once and you are done.
Drag it onto the drop area or click to browse your disk. It accepts images, PDF documents, video, audio, office files and ZIP archives.
Type the size in megabytes that must not be exceeded. If you are not sure, check the place you are uploading to: it usually states the limit before throwing the error.
Compression happens on your machine and the file is ready to save. You will see the original size, the size achieved and how long it took.
What happens under the hood for each format, and what to expect.
A PDF is heavy because of the images inside it, almost never because of the text. First the document is rewritten losslessly, which already trims a lot in files exported from a word processor. If the target is tighter, the pages become images: far smaller, but the text stops being selectable, which is why you are warned before it is handed over.
For photographs, JPG beats PNG at the same size; for screenshots and graphics with flat areas it is the other way round. When the target is demanding it is better to drop resolution than quality: a slightly smaller image looks better than one of the same weight full of blocks. HEIC photos from phones and TIFF scans are converted to a format any device can open.
A video weighs what it weighs because of duration, resolution and how much the scene moves. Trimming what you do not need usually wins more than any quality setting. The app re-encodes with your system codec and, if the target does not fit at the original resolution, steps it down rather than wrecking the picture.
With audio the size is almost proportional to the bit rate, so the result is predictable. Speech tolerates far more reduction than music before anyone notices: a spoken recording can be made much lighter before it starts to suffer.
In a text document or a slide deck, the weight is almost always the photos and screenshots pasted inside. The package is opened, those images are reduced and it is closed again keeping the structure, so the file still opens normally. A ZIP gets the same treatment.
Mail providers reject attachments above a certain weight. Setting the target a little below it avoids the bounce and the second attempt.
Many upload forms cut off by size and return an unhelpful error. Compressing first saves filling the form in twice.
Messaging apps re-compress on their own and spoil the quality. Sending a file that already fits preserves the result far better.
Heavy images are the most common reason a page loads slowly. Reducing them improves the visitor experience and the performance score.
A cloud compressor needs your file to travel to someone else’s computer, be processed there and come back. That means waiting for the upload, trusting what the service does with a copy of your document and depending on its server being up.
Here the maths runs on your own machine. There is no upload to wait for, no copy to delete afterwards, and it works just the same with the connection down. The honest trade-off is that your computer sets the speed: on an old laptop a long video will take longer than on a recent machine.
Why files weigh what they weigh, and how far to bring them down.
A twenty-page document can take up forty megabytes or two hundred kilobytes with the same visible content. The difference is almost never the text.
Set the number too low and you ruin the file; set it too high and it gets rejected. These are the rules that work without guesswork.
Drop the file in, type the maximum size in megabytes and hit compress. Filely tries different quality levels and keeps the best one that fits under that figure, so the result never exceeds what you asked for.
It depends how hard you push. With a comfortable target the loss is imperceptible; when the target is demanding, the app would rather drop resolution than fill the image with artefacts. For PDFs it first tries a lossless pass that does not touch a single pixel.
No. Compression runs on your own processor, inside the browser tab. There is no upload, no account needed and no copy left anywhere: close the tab and nothing remains.
Images in JPG, PNG, WEBP, HEIC and TIFF; PDF documents; video in MP4 and MOV; audio in MP3 and WAV; animated GIF; and office packages in DOCX, PPTX and XLSX, plus ZIP archives.
There is no daily quota and no weight cap imposed by the app. The only real ceiling is the memory your browser can reserve, and you are warned before starting if a file gets close to it.
Yes. Once loaded, the app is stored in your browser and keeps compressing with the connection switched off. That is the logical consequence of depending on no server at all.
Yes, and it is the first thing attempted: an internal rewrite that keeps the text selectable and searchable. Only if that path falls short of the target do the pages become images, and you are told when that happens.
Because your machine does the work. An image resolves in seconds; a long video has to be re-encoded end to end and can take minutes. A computer with more cores and more memory will be faster.