Privacy · Compression
A private image compressor. Files never leave your device.
Most online compressors work by uploading your photo to someone else's server, holding it, then deleting it later. FormatTailor removes that step entirely — compression runs in this tab, and the only copy of your file is yours.
The honest comparison
Three ways image compression handles your file.
Each model quoted from its own documentation. Upload-and-delete services are not malicious — they are simply a different architecture with a different risk surface.
| Model | Example | What happens to your file |
|---|---|---|
| In-browserFormatTailor | This site | The source is decoded inside your browser tab and never transmitted. There is no upload step, no storage window, and nothing to delete. Closing the tab clears the session. |
| In-browserSquoosh | squoosh.app | Single-purpose client-side demo app. Its own words: “Images never leave your device since Squoosh does all the work locally.” |
| Upload & deleteTinyPNG / Tinify | tinypng.com | Files are uploaded for server-side processing. Its terms state: “Submitted content will be stored for a maximum of 48 hours.” (Tinify terms) |
Why the difference matters: with no upload there is no transmission to intercept, no retention policy to take on faith, and no server copy that could outlive a policy change. For screenshots, ID documents, or location-bearing photos, removing the step removes the whole category of risk.
Opening the local image workspace…
Opening the local image workspace…
Hard limits today?
Pre-set targets for common ceilings.
Each route opens the same local compressor locked to one format and ceiling.
Questions about private compression.
Is an upload-based compressor unsafe?
Not inherently. Reputable services state retention limits and delete files on schedule — TinyPNG’s terms commit to a maximum 48-hour storage window. The difference is exposure: a local tool has no upload step, so there is no retention window to trust in the first place.
Does local compression cost quality?
No. The compressor searches encoder quality toward your target size exactly as server tools do — the encoding happens on your device instead of a data centre. You inspect the actual result before downloading.
What are size-target routes?
Pages like /compress-jpg-to-100kb/ open this same compressor pre-set to a specific ceiling for one input format, useful when a portal or form enforces a hard limit today.