100% Local · No Upload · No Watermark

Discord GIF Compression Tests

Updated November 13, 2026. This page documents how we measure whether our Discord presets hit their byte targets. We publish the method first, then fill in before/after sizes from a fixed sample set—no invented megabyte numbers. Use the Discord compressor on this page or the dedicated Discord tool to run the same presets locally.

Tier: Free · 20 MB ✓
Advanced

Built for Discord uploads

Tier-aware targets, channel-friendly output, private compression.

What we measure

For each sample GIF we record: preset (Discord Free 20MB, Discord Safe 8MB, or a Nitro tier), original file size, compressed file size, whether the output is at or under the target, and the compressor settings shown in the UI.

Results table (numbers pending)

Columns: Sample | Target preset | Before (MB) | After (MB) | At or under target? | Notes. Rows stay empty until we run the fixed sample set and commit the measured sizes. The method is published first; before/after megabytes will appear here only after that run is stored.

Where to compress

Run the same tests on the live GIF Compressor for Discord or the homepage Online GIF Compressor, or use the tier picker embedded on this page. Download the result and check size in your file manager or OS properties.

How it works

1

Pick a fixed sample set We will use a small set of labeled test GIFs (short loop, long loop, wide screenshot, high color) stored with provenance in the repo. Until that set lands, treat the table above as a placeholder.

2

Compress with a Discord preset Open gifcompressor.app, choose Discord Free 20MB or Discord Safe 8MB (or a Nitro tier when testing those limits), compress, and download the .gif.

3

Record sizes honestly Note the original and downloaded byte sizes. If the tool reports “target reached,” confirm on disk. Do not publish rounded or guessed megabytes—only measured values.

Frequently asked

Why are there no before/after megabytes yet?
We would rather ship the method and an empty table than fake numbers. The fixed sample set has not been checked in yet, so this page does not list before/after sizes. When that run is stored, this page will be updated with the same measured values.
Which Discord targets do you test?
Primary rows use Discord Free 20MB and Discord Safe 8MB—the same presets as the GIF Compressor for Discord. Optional rows can cover Nitro Basic 50MB and Nitro 500MB when those tiers apply to the uploader’s account. You can also start from the homepage Online GIF Compressor or Compress GIF to 10MB when you need a different target.
What is the maximum input file size?
Each GIF you add to the tool can be up to 200 MB, matching the dropzone label. That is the input limit per file. Preset targets such as Discord Free 20 MB, Discord Safe 8 MB, or Nitro 500 MB are output goals for the compressed result—they do not increase how large a source file you can drop in.
How can I verify files stay on my device?
Open DevTools → Network, compress a GIF, and confirm no request sends your file bytes to gifcompressor.app (only static assets and WASM should load). You can also revisit the page offline after the first load and compress again. Stayput and ShrinkBee also describe browser-side compression—use the same Network check on any tool before you trust a privacy claim.
Does this upload my GIF?
No. Compression is designed to run locally in your browser with WebAssembly—the GIF is read from your device and the compressed .gif is downloaded from memory, not from our servers.

More GIF tools