Discord accepts a video you can already play in your browser by trimming a bounded section of the source clip locally — under 10 MB on a free account, 50 MB on Nitro Basic — and saving the result as a WebM file. The whole pipeline — decode, seek, stream capture, encode, download — runs inside the current tab, so the source video never leaves your device. That matters because Discord's upload caps punish long clips regardless of how clean they look, and trimming duration usually beats compressing bitrate for keeping motion sharp in a short message. The Video Trimmer takes one local file, reads its true decoded duration, accepts decimal start and end times expressed as seconds, and rewrites only the range you select. Output is WebM because the tool relies on the browser's built-in MediaRecorder codecs instead of a server processing. That trade-off keeps the page light and avoids uploading, but it also means a few rules about source files and the resulting clip that are worth reading before you trim.
Discord Upload Caps and Why Trimming Helps
Discord sets a hard ceiling on what free and Nitro accounts can attach in a channel message. Free accounts cap at roughly 10 MB per upload; Nitro Basic, Nitro, and Nitro Classic tiers raise that ceiling to 50 MB, with the highest Nitro tier reaching 500 MB depending on the rollout region. Those numbers come from Discord's published help center and have been stable for years, so they are a reliable planning target rather than a moving rule. A 30-second 1080p H.264 clip almost always sits above 10 MB once you factor in audio; a two-minute clip is comfortably over even the 50 MB Nitro Basic ceiling. Two paths get a video under the cap: compress it more aggressively, or cut the duration. Compressing trades pixels for file size, and Discord's preview re-encodes uploads a second time, so a heavily compressed source can look noticeably soft in chat. The encoder only re-records the selected range, and the output preserves the source dimensions. For most "share a funny moment" or "show this one clip" use cases, trimming is the better trade.
Trim a Video for Discord in Three Steps
- Open the Video Trimmer and pick a supported local file. Wait until the duration field populates with the decoded length. The tool accepts MP4, WebM, MOV, M4V, and Ogg containers up to 500 MiB; the decoded source must be no longer than five minutes and within the browser's pixel limits (no wider or taller than 4096 px, and no greater than 3840 × 2160 total area).
- Enter the start and end times as decimal seconds. The start must be zero or greater, the end must be later than the start, and both values must fall inside the populated duration. The selected clip must be at least 0.1 seconds long — reversed or out-of-range values fail visibly rather than being silently clamped.
- Select Trim video. The UI reports the requested duration and the output size. When the encode finishes, download the WebM file. Cancel stops an active job if you change your mind mid-record.
Input Limits and Codec Compatibility
Three constraints decide whether the Video Trimmer can complete the task for your source. Container format, decoded duration, and pixel dimensions are explicit. A fourth, less visible constraint is the codec inside the container: the browser has to decode the audio and video tracks to expose a media stream, and a familiar extension such as .mp4 does not guarantee success because the codecs inside the container (H.264, H.265, AAC, and friends) must be supported by your specific browser build. If your browser cannot decode the track, the duration field will not populate, and the tool will not advance. For wide compatibility, an MP4 with H.264 video and AAC audio decoded by Chromium-based browsers or Firefox is the safest bet; Ogg with Theora is also broadly supported. WebM with VP9 or VP8 video and Opus audio is the most reliable across browsers because the encoder path itself uses those codecs. If a file with a supported extension fails to populate duration, the issue is the codec, not the filename.
| Container | Browser decode support | Notes |
|---|---|---|
| MP4 (H.264 + AAC) | Strong in Chromium, Firefox, Safari | Safest container for input |
| WebM (VP9/VP8 + Opus) | Strong everywhere | Matches the encoder output codec |
| MOV (H.264 + AAC) | Strong in Safari and Chromium | Chromium support depends on build |
| M4V | Similar to MP4 | Often a renamed MP4 with Apple metadata |
| Ogg (Theora + Vorbis) | Strong in Firefox and Chromium | Older, but still decodeable |
Output Format and Boundary Behavior
The Trimmer records during real-time playback, so the encoded output is a fresh WebM whose duration matches the range you requested, with dimensions preserved from the source. Several properties of the source do not survive the trip: the exact keyframes, the precise color metadata, the original audio channel layout (it may be downmixed), the exact file size (it will differ), and the precise duration. Because MediaRecorder samples playback time rather than exposing frame-accurate cut points, the last encoded frame can land a small fraction of a second around your requested end. For a Discord clip where the goal is "this moment, not that moment," that drift is invisible. For a broadcast cut that needs to land on a specific beat or visual cue, it is not enough. The generated WebM does receive the selected duration in its Segment Info, so compatible players (Discord's preview, VLC, browsers) report a finite timeline instead of an unbounded stream. Cancel stops active work.
Trimming vs. Compressing vs. Resizing for Discord
Different tools solve different Discord prep problems. Trimming is for "this video is too long" — the source itself is fine, only the duration is the problem. Resizing is for "this video is too tall or too wide for the channel preview" — usually a vertical 9:16 phone clip meant for a non-TikTok channel, or a wide 21:9 cinematic capture that Discord's player letterboxes awkwardly. Compressing is for "this clip is the right shape and length but the file is too big" — bitrate math, not pixel work. Most Discord prep is a chain: trim the boring intro and the trailing silence, then resize if the aspect ratio is wrong, then compress only if the file is still over the upload cap.
| Task | Best tool | What it changes |
|---|---|---|
| Cut a section from a local video for Discord | Video Trimmer | Duration |
| Resize an oversized video for Discord without uploading | Video Resizer | Width × height, aspect preserved or set |
| Compress a video for Discord at 10 MB or less | Compress a Video for Discord at 10 MB or Less | Bitrate, file size |
For the specific case of fitting a clip under Discord's free 10 MB cap, the bitrate math is straightforward. File size in bits equals bitrate multiplied by duration; a 10 MB ceiling is 80 megabits (10 × 8). At a balanced WebM encode of roughly 2 Mbps (2,000 kbps) for video plus a small audio track, the maximum duration is approximately 80 megabits divided by 2 megabits per second, which works out to around 40 seconds of footage. That number is a planning estimate, not a guarantee, because real-world audio and keyframe overhead will shave a few seconds off it. If the clip you want to share is under that ceiling, trimming alone is enough; if it is over, compression is the next step.
When the Local Trimmer Is Not Enough
A few Discord prep tasks fall outside what the Video Trimmer can deliver. It cannot fetch a YouTube link or any remote URL — the source must be a local file already on your device. It does not remove watermarks, bypass DRM, or strip copy protection; using it on protected content is not the intended path. It does not preserve every metadata field from the source, so if your camera writes timecode, GPS, or lens data that you need later, expect that data to be missing from the WebM output. It does not produce an MP4 with H.264 — the output is WebM using the browser's available VP9, VP8, and optional Opus combinations, and Discord accepts WebM uploads natively, but some external platforms and editors do not. For multitrack audio, exact keyframe cuts on a beat, subtitle preservation, or footage longer than five minutes decoded, a dedicated desktop editor is the right tool. For everything else — a 30-second reaction clip, a tutorial moment, a five-minute game highlight — opening the Video Trimmer, entering two numbers, and downloading the WebM is the entire workflow.