Compress images without uploading originals.
Drop an image, tune quality and resize settings, then download WebP or AVIF results from your browser. The original file stays on this device with a no upload workflow.
Privacy-first by default
Image conversion runs client-side. Server upload routes, GA4 tracking, filenames, and EXIF collection stay out of the compression workflow, and privacy rules are linked before the footer.
Browser image tools
How to use it
- 1
Add local images
Drop one or more images into the work area or choose files from your device. The original files stay in the browser session and are not uploaded for conversion.
- 2
Tune output settings
Adjust quality, resize limits, metadata handling, and output format before compression. Use WebP for broad compatibility or AVIF when smaller modern-browser output is the priority.
- 3
Review estimated results
Check size changes, output names, and per-file status before downloading. This keeps batch work predictable when you are preparing several images for the same page or document.
- 4
Download browser-side output
Save each compressed image or export a ZIP package. Results are generated locally, so you can repeat settings without creating an account or waiting for server processing.
Common use cases
Security and privacy
Privacy-first compression
Frisbly is designed around a no-upload image workflow. Compression uses browser APIs and local WebAssembly processing instead of server upload routes for original files. The page does not need an account, and the tool content is written to avoid collecting filenames, EXIF, user identifiers, or image contents for analytics. If you close the tab, the selected source files leave the session with the browser state.
Supported inputs and outputs
Supported inputs and outputs
- JPEG and PNG inputs for common web and document images.
- WebP and AVIF output workflows for smaller browser-ready files.
- Optional resize and quality settings for repeated publishing tasks.
- Single-file downloads and ZIP export for batch compression.
FAQ
Are images uploaded during compression?
No. The compression workflow is built for browser-side processing, so original images remain on your device instead of being sent to a server conversion route.
Which image formats should I choose?
Use WebP when you need strong compatibility across current browsers. Use AVIF when the smallest modern output is more important and your target browsers support it.
Can compression remove metadata?
The workflow keeps metadata handling visible so you can prepare lighter copies without depending on hidden server-side cleanup. Always inspect sensitive files before sharing them publicly.
Does quality affect dimensions?
Quality changes compression strength, while resize settings change pixel dimensions. Use both when you need a smaller image that also fits a fixed layout.
Can I process multiple images?
Yes. Batch work is supported so repeated settings can be applied and downloaded without creating an account or uploading source files.