Save Replay
Discord clip sharing11 min read

How to Share a Large Gameplay Video on Discord

Discord limits attachments by file size, so a short, high-bitrate recording can fail even when its duration looks reasonable. Check the limit that applies to you, keep only the moment the conversation needs, and decide whether the result belongs in Discord as an attachment or as a watch link.

Published by Save Replay · July 19, 2026 · Updated August 25, 2026

Direct answer

Direct answer

Discord's File Attachments FAQ says the free upload limit is 20 MB as of August 2026, but its separate Account Caps page still lists 10 MB for a base account. Both sources list 50 MB for Nitro Basic and 500 MB for Nitro. Boosted servers can provide 50 MB at Level 2 or 100 MB at Level 3. Check the limit shown in your client before exporting. If a recording is too large, trim it first, then attach the smaller result or share a Save Replay watch link.

20 MB

Free upload FAQ

Discord's separate Account Caps table still lists 10 MB for a base account.

50 MB

Nitro Basic

The documented personal limit for Nitro Basic.

500 MB

Nitro

The documented personal limit for Nitro.

A practical framework

Work through the decision in four steps

  1. 1

    Check the cap that applies

    Discord's current help pages disagree on whether the free limit is 20 MB or 10 MB. Check the value shown in your client, then compare the file size with your plan and, when relevant, the server's boost level.

  2. 2

    Cut before you compress

    Keep the setup and result, remove queues or dead time, and preview the exact segment. Trimming reduces size without spending bits on footage nobody needs.

  3. 3

    Choose attachment or link

    Attach a file that fits when playback inside chat is the priority. Use a hosted watch link when preserving a useful clip matters more than fitting the attachment cap.

  4. 4

    Send context with the video

    Name the moment, tell viewers what to notice, and open the attachment or link once before posting it to a busy channel.

Choose the workaround that matches the job

Choose the workaround that matches the job
OptionBest whenMain tradeoff
Trim the recordingOnly one part of the source mattersYou must choose a clear start and end
Share a watch linkQuality and a dedicated viewing page matterViewers open the clip outside Discord
Compress to a target sizeThe file must play as a Discord attachmentLong or high-motion video can lose visible detail
Use Nitro or server boostsLarge attachments are a recurring needIt adds an ongoing subscription or server cost
Split into partsEvery part must remain an attachmentThe conversation and viewing order become harder to follow

Discord's current free-upload documentation is inconsistent

Discord's File Attachments FAQ, updated in August 2026, says the free upload limit increased from 10 MB to 20 MB. Its Account Caps page still lists 10 MB for a base account. The same FAQ says Discord experiments with upload sizes for selected users. Treat the limit displayed by your Discord client as the final check before preparing a file around a hard cap.

The official pages agree on the paid personal limits: 50 MB for Nitro Basic and 500 MB for Nitro. Discord's server caps list 50 MB uploads for all members at Boost Level 2 and 100 MB at Level 3.

Duration alone cannot tell you whether a video fits. File size grows with the combined video and audio bitrate, plus a small amount of container overhead. A short 1080p gameplay clip with fast motion can be larger than a longer, quieter screen recording encoded at a lower bitrate.

  • Free account: 20 MB in the File Attachments FAQ; 10 MB in the separate Account Caps table
  • Nitro Basic: 50 MB documented personal limit
  • Nitro: 500 MB documented personal limit
  • Boosted server: 50 MB at Level 2 or 100 MB at Level 3 for all members

Trim before compressing when the source contains dead time

A replay buffer or screen recording often contains menus, loading, failed attempts, or several minutes around a ten-second event. Remove those parts first. The remaining video keeps more of its original detail because the encoder does not have to force every irrelevant second into the same file-size budget.

Place the start point before the cause of the moment and leave the result on screen long enough to register. For gameplay, that might include the score, the callout, or the position that makes the play understandable. For a bug report, keep the initial state, the action, and the failure. Preview the selected range with sound before uploading it.

Compress only when the result must be a Discord attachment

Target-size compression is useful when viewers need an attachment that plays inside the Discord message. Estimate the total bitrate in kilobits per second with `(target MB x 8,192) / duration in seconds`, then reserve part of that budget for audio and a safety margin for the container. If your client shows a 10 MB target, a 60-second file has a theoretical total of about 1,365 kbps before those deductions.

That budget is tight for detailed 1080p footage, especially fast gameplay or screen recordings with small text. Shorten the selection, lower the resolution, reduce frame rate where appropriate, or accept more compression. Leave headroom below the exact cap because metadata, audio, and container overhead can push a borderline export over the limit.

Use a format Discord can present predictably

Discord's File Attachments FAQ currently lists MOV and MP4 among common video attachments. For MP4, it explicitly lists H.264, HEVC/H.265, and AV1. Actual playback can still depend on the recipient's device and client, so test the exported file in the Discord client you plan to use rather than relying on a renamed extension.

An extension is only the container label. Renaming an MKV or WebM file to `.mp4` does not convert its video and audio streams. Export or remux to the format you intend to send, then play the result from start to finish before deleting the source.

Make the clip safe and useful inside a fast-moving chat

People should not have to scrub through a match to find the point of your message. Add one sentence beside the attachment or link. 'Watch the minimap before the final push' gives the viewer a job; an unexplained URL does not.

Review voice chat, player names, account identifiers, notifications, private messages, and overlays before uploading. Public access is suitable only for intentional broad sharing. An unlisted Save Replay URL avoids intentional search discovery but remains forwardable by anyone who has it. Use password-protected access when a shared secret is appropriate, or private access when only the owner should be able to watch.

Source notes

External product conditions can change. These primary sources were reviewed for this article; check them again before making a plan-dependent decision.

Put the workflow into practice

Choose the moment before you upload it

Preview locally, select the range you want, and create one browser-ready link without an account for the basic flow.

Next reading

Check current limits, get support, and review the Privacy Policy and Terms.