How to compress game clips for Discord
Updated November 19, 2026
You saved a great round with OBS, the NVIDIA overlay, AMD’s software or the Xbox Game Bar, dragged it into Discord, and it was too big. Game recordings are about the hardest videos to squeeze under a chat limit. This guide explains why they come out so large, which capture settings help, how to cut a clip down to the moment that matters, and what to expect when a 60 fps highlight has to fit in 20 or 50 MB. For Discord’s current limits by plan and a broader list of fixes, see Discord file too large? 5 ways to send big videos.
Why game recordings are so big
Three things stack up:
- High bitrates. Capture tools encode in real time on your graphics card while the game is running. To keep quality up without slowing the game, they spend a lot of bits, often tens of megabits per second. A recording at 50 Mbps fills about 375 MB a minute, so Discord’s free 20 MB limit holds only about 3 seconds of it.
- 60 fps or more. Twice the frames of a 30 fps video means roughly twice the data at the same quality per frame.
- Hard content. Fast camera turns, particles, foliage and explosions change most of the picture from one frame to the next, and that is exactly what video compression handles worst.
So a recording that is fine on your disk is far too big for chat, and simply shrinking it to 20 MB has to throw a lot away. You get better results by recording smarter, keeping only the highlight, and letting the frame rate drop when the budget is tight.
Recording settings that make smaller clips
Every capture tool lets you change the same few things: resolution, frame rate, and bitrate or a quality preset. Menu names move between versions, so treat this as where to look rather than an exact path.
| Tool | Where to look | Settings that affect size |
|---|---|---|
| OBS Studio | Settings → Output and Settings → Video | Recording quality (Simple mode) or bitrate and rate control (Advanced mode); output resolution; FPS |
| NVIDIA app or GeForce Experience (formerly ShadowPlay) | The in-game overlay (Alt+Z by default), video capture settings | Quality, resolution, frame rate, bitrate; Instant Replay length |
| AMD Software: Adrenalin Edition | Record & Stream settings | Resolution, frame rate, bitrate; Instant Replay length |
| Xbox Game Bar (Windows) | Windows Settings → Gaming → Captures | Video frame rate (30 or 60 fps), video quality, how much “record what happened” keeps |
A few choices make a real difference:
- Record at 30 fps if you mostly share clips and don’t edit them. It roughly halves the size for the same look per frame. Keep 60 fps if you play fast shooters and smooth motion is the point of the clip.
- Shorten the instant replay window. If your replay buffer saves the last 5 minutes, every clip starts out 5 minutes long. Fifteen to thirty seconds catches most highlights.
- Don’t lower the bitrate too far. A low recording bitrate makes every clip permanently worse. Recording at good quality and compressing only the highlight usually looks better than recording at a low bitrate, because the final encode can take its time and doesn’t have to keep up with the game.
Trim to the highlight first
The size limit is fixed, so every second you cut leaves more bits for the seconds you keep. At 20 MB, a 15-second clip gets about 9.7 Mbps of video, while a full minute gets about 2.3 Mbps and drops to 720p. Trimming is the single biggest quality win.
- In the capture app. Many capture tools have a basic trimmer in their gallery. OBS doesn’t; use another tool for its recordings.
- In Windows. Clipchamp (included with Windows 11) can trim, as can many free editors.
- In SizeClip. Open More options, play the preview, and use the buttons to set the start and end, or type the times. Trimming and compressing happen in one pass.
- With ffmpeg.
ffmpeg -ss 00:02:15 -i input.mkv -t 20 -c copy highlight.mkvcuts 20 seconds without re-encoding. It is fast and lossless but snaps to a keyframe, so the start can be off by a second or two, and the result is usually still far over 20 MB.
What SizeClip does with a 60 fps clip
SizeClip works out how many bits each pixel of each frame would get. When a source above 31 fps would get too few, it encodes at 30 fps instead (25 fps for 50 fps sources), so every frame gets twice the bits. For a 1080p 60 fps clip with sound, that means 60 fps is kept up to about 19 seconds at 20 MB and about 48 seconds at 50 MB. The frame rate is decided once, on the first pass; if the file comes out over the target, SizeClip runs up to two more passes at a lower bitrate without changing the frame rate. Tick Keep original frame rate under More options to never drop frames.
We measured both settings on a 20-second 1080p 60 fps test clip (30.5 MB, a synthetic moving test pattern, not real gameplay) at Discord’s 20 MB size, in a desktop Chromium browser. Times will be different on your device.
| Setting | Output | Resolution and frame rate | Time |
|---|---|---|---|
| Keep original frame rate off (default) | 19.2 MB | 1080p, 30 fps | 5.3 s |
| Keep original frame rate on | 18.7 MB | 1080p, 60 fps | 17.9 s |
Both fit. The 20-second clip is just past the 19-second line, so by default it went to 30 fps, with each frame getting about twice the bits. With the option on, it kept 60 fps at 1080p, and the encode took over three times as long here. On real gameplay, the 60 fps version will usually look smoother but softer in busy scenes. If your clip is a quick flick or a movement trick, smoothness may matter more; for a funny moment or a scoreboard, sharper 30 fps is usually the better trade.
Quality vs. length at 20 MB and 50 MB
These are the settings SizeClip plans for a 1080p 60 fps recording with sound at Discord’s free 20 MB and Nitro Basic 50 MB sizes, with the frame-rate option off. They come from its planning logic, so they show what it aims for, not how every clip will look.
| Clip length | At 20 MB | At 50 MB |
|---|---|---|
| 10 seconds | 1080p, 60 fps, ~12 Mbps | 1080p, 60 fps, ~12 Mbps |
| 15 seconds | 1080p, 60 fps, ~9.7 Mbps | 1080p, 60 fps, ~12 Mbps |
| 30 seconds | 1080p, 30 fps, ~4.8 Mbps | 1080p, 60 fps, ~12 Mbps |
| 45 seconds | 1080p, 30 fps, ~3.1 Mbps | 1080p, 60 fps, ~8.1 Mbps |
| 1 minute | 720p, 30 fps, ~2.3 Mbps | 1080p, 30 fps, ~6.0 Mbps |
| 2 minutes | 480p, 30 fps, ~1.1 Mbps | 1080p, 30 fps, ~2.9 Mbps |
| 3 minutes | 480p, 30 fps, ~0.7 Mbps | 720p, 30 fps, ~1.9 Mbps |
| 5 minutes | 360p, 30 fps, ~0.4 Mbps | 480p, 30 fps, ~1.1 Mbps |
Bitrates are for video; audio adds 128 kbps (less for the longest clips). At 1080p SizeClip never spends more than 12 Mbps, and never more than about 85% of the source’s own video bitrate, so short clips can come out well under the limit. With Keep original frame rate on, the resolution and bitrate stay the same but the bits are spread over twice as many frames. As a rule of thumb, fast gameplay looks good at 20 MB up to about 30 seconds and is watchable up to a minute; past two minutes, consider the 50 MB size if you have Nitro Basic, or a cloud link.
Doing it with ffmpeg
If you’d rather use the command line, two-pass encoding with a fixed bitrate gets close to a size. Work out the budget first: 20 MB is 160 megabits, so a 30-second clip can average about 5,300 kbps in total. Take off 128 kbps for audio and about 10% for safety, and 4,600 kbps of video is a sensible choice. These commands cut 30 seconds starting at 2:15, drop to 30 fps and encode in two passes:
ffmpeg -y -ss 00:02:15 -i input.mkv -t 30 -vf fps=30 -c:v libx264 -preset medium -b:v 4600k -pass 1 -an -f null /dev/null
ffmpeg -ss 00:02:15 -i input.mkv -t 30 -vf fps=30 -c:v libx264 -preset medium -b:v 4600k -pass 2 -c:a aac -b:a 128k -movflags +faststart highlight.mp4
On Windows, use NUL instead of /dev/null. Because the video is re-encoded, the cut starts on the exact frame. Remove -vf fps=30 to keep 60 fps, and add scale=-2:720 (as -vf fps=30,scale=-2:720) for longer clips. The exact file size guide explains the math in more detail.
Quick checklist
- Keep the replay buffer short so clips start small.
- Trim to the highlight before anything else.
- Under about 19 seconds, a 60 fps clip stays at 60 fps at 20 MB on its own.
- Longer than that, accept 30 fps for a sharper picture, or tick Keep original frame rate for smoothness.
- Past two minutes, try the 50 MB size if your plan allows it, or share a link.
SizeClip is an independent tool. It is not affiliated with or endorsed by Discord, NVIDIA, AMD, Microsoft or the OBS Project; their product names are used only to describe where settings are.
Frequently asked questions
Should I record in MKV or MP4?
OBS has long recommended MKV because a regular MP4 can be unreadable if the recording is cut off by a crash. Newer OBS versions also offer crash-safe (fragmented) MP4 and MOV options. You can convert MKV to MP4 in OBS with File → Remux Recordings, but you don’t need to for SizeClip: it accepts MKV, MP4, MOV and WebM and always saves an MP4.
Why does my compressed clip look less smooth than the original?
It was probably encoded at 30 fps. SizeClip does that for high-frame-rate clips when the bitrate is too low to give 60 frames a second enough detail. Tick Keep original frame rate under More options, or trim the clip shorter so 60 fps fits.
Can I keep a 1440p or 4K recording at full resolution?
Not in SizeClip: it outputs at most 1080p on the shorter side, and at Discord-sized limits even 1080p is only reachable for short clips. Most people watch Discord clips in a small chat window or on a phone, where 1080p or 720p looks fine.
Do I need to install anything?
No. SizeClip runs in your browser using its built-in video encoder, so there is nothing to install and the clip is never uploaded. Recent Chrome and Edge are fastest; Safari on a recent Mac also works.