Triim vs TinyPNG for transparent images
These tools get compared a lot but they aren't really substitutes. TinyPNG reduces the file size of an image by compressing the bytes more aggressively. Triim shrinks the image's canvas by removing transparent edges, removes solid backgrounds to create transparency, and converts between formats. They solve different problems and they pair well.
The short version
If your PNG has extra transparent space around the subject, Triim first — trimming the canvas removes pixels entirely and is usually the bigger size win on logos/UI assets. If after trimming you still want to squeeze more bytes out of the PNG, run it through TinyPNG. If you can afford to switch formats, use Triim's converter to ship WebP — usually a bigger size win than either tool alone.
What each tool actually does
TinyPNG
TinyPNG runs a perceptual quantization pass on PNG and JPEG files. For PNGs that means reducing the color palette in a way the human eye barely notices and re-encoding. The result is the same dimensions, same format, same transparency, fewer bytes. It is excellent at what it does.
Triim
Triim is a suite of browser-only tools:
- Trim — crops the canvas to the bounding box of the non-transparent pixels.
- Remove BG — converts a solid background to transparency.
- Square — pads to a 1:1 canvas.
- Resize — changes pixel dimensions.
- Convert — switches between PNG, WebP, and JPEG with a quality slider.
None of those are byte-level recompression on a same-format file. They change shape, dimensions, or format.
Why trimming often beats compressing
A PNG with 30% empty transparent space at the edges has roughly 30% more pixels than the version with that space removed. PNG's compression handles long runs of transparent pixels efficiently, so the size win isn't exactly proportional — but on assets exported with generous padding (icons, sprite frames, UI parts) trimming often beats palette quantization for the same starting file.
The bigger point: trimming changes the image's actual content. A subsequent compression pass on a smaller canvas has less work to do, and the two are additive.
When to use which
| Goal | Tool | Why |
|---|---|---|
| PNG has empty transparent borders | Triim trim | Crop wasted pixels. Free size win, no quality loss. |
| PNG is already tight, still too big | TinyPNG | Palette + entropy compression. |
| Can ship modern format | Triim convert → WebP | Usually bigger savings than compressing PNG. |
| Product shot on white | Triim remove-bg + trim | Create transparency, then crop. |
| JPEG photograph | TinyPNG (or Triim convert with low quality) | JPEG has no alpha; nothing to trim. |
| Bulk batch of mixed needs | Both, in order: Triim then TinyPNG | They're complementary, not competing. |
Privacy and pricing
TinyPNG uploads files to their servers to compress them. The free tier limits the count per month; paid plans raise the limit. Triim doesn't upload at all — every operation runs in your browser — so there are no per-month limits and nothing to pay for.
A reasonable workflow
- Drop your PNGs into Triim to trim transparent borders.
- If the assets can ship as WebP, run them through Triim's converter at 85–90% quality.
- If you still need more bytes off and you're shipping PNG/JPEG, send the result through TinyPNG.