Key Twitter video specs at a glance
Quick reference table for the most common requirements when posting video on X (formerly Twitter).
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Supported formats | MP4, MOV, AVI, FLV, WMV, WebM, MKV | Platform documentation |
| Max file size | 16 GB | Platform documentation |
| Max duration (video) | 144 seconds (2 min 24 s) for video; longer for X Spaces Audio | Platform documentation |
| Aspect ratios | 16:9, 9:16 (vertical), 1:1 (square), 2:1 | Platform guidance |
| Recommended resolution | 1280 x 720 (minimum); 1920 x 1080 for HD | Platform guidance |
| Codec | H.264/AVC for video; AAC or MP3 for audio | Platform documentation |
| Captions/subtitles | Recommended; supported formats include SRT, VTT | Platform guidance |
Why specs matter on X
Videos that meet technical expectations load faster, play reliably across devices, and are more likely to be recommended byX’s distribution systems. Upload errors, re-encoding delays, or muted playback can all arise from ignoring format, size, or caption rules. Understanding evergreen requirements helps you reduce friction, preserve intent, and reach more people over time.
Accepted file formats and when to use them
X supports a wide set of container and codec combinations. Choosing the right format reduces conversion steps and preserves quality.
- MP4: Best all-purpose container with broad compatibility and efficient H.264/HEVC support.
- MOV: Common from macOS and ProRes workflows; supported but often larger.
- AVI, FLV, WMV: Legacy formats accepted, but prefer MP4 for reliability.
- WebM / MKV: Useful for VP9/AV1 content; verify playback on your target devices.
Container vs codec
The container (e.g., MP4) holds video, audio, and metadata. The codec (e.g., H.264) compresses the video. For maximum reach, deliver an MP4 wrapped with H.264 video and AAC audio. This setup minimizes transcoding surprises and ensures consistent audio across devices.
Duration, timing, and audience retention
Keep videos between 15 and 90 seconds when possible for strong completion rates. Short hooks in the first three seconds reduce early drop-off. For longer-form content up to 144 seconds, place key messages early and use chapters or timestamps. X Spaces Audio streams can exceed standard video duration limits; plan length around topic depth and attention span rather than platform ceilings alone.
Resolution, bitrate, and bandwidth considerations
Resolution and bitrate directly affect visual quality and buffering risk. Higher is not always better if file size impedes upload speed or causes re-encode issues.
| Metric | Estimate or Range | Context |
|---|---|---|
| Minimum recommended resolution | 1280 x 720 | Ensures stable playback on most feeds |
| Recommended resolution for quality | 1920 x 1080 (1080p) | Standard HD for clear visuals |
| File size cap | 16 GB | Rarely reached; allows long-form uploads within policy |
| Aspect ratios supported | 16:9, 9:16, 1:1, 2:1 | Choose based on primary audience devices |
Audio, captions, and accessibility
Audio quality and clarity are as important as video. Use AAC or MP3 stereo at a stable bitrate (e.g., 128–192 kbps) to avoid dropouts. Add captions or subtitles in SRT or VTT to support accessibility, sound-off viewing, and discovery in search. Captions also help the algorithm by making spoken content text-indexed.
Upload and delivery best practices
Reduce upload failures and re-encoding wait times with simple prep steps. Use a wired connection when possible, close bandwidth-heavy apps, and avoid peak network congestion for large files. Prefer native MP4 files over wrapped project files, and double-check aspect ratio and audio levels before publishing.
- Check format compatibility with X’s current documentation before batch uploads.
- Test playback on mobile and desktop before promoting the tweet.
- Use consistent naming and clear captions to improve recall and reach.
Common pitfalls and how to avoid them
Violating duration, format, or size expectations can lead to upload errors or poor playback. Mismatched aspect ratios may force cropping or black bars; unoptimized bitrates cause buffering. Always review platform guidance before major campaigns, and keep a checklist for format, resolution, captions, and file size.
Summary checklist for reliable Twitter (X) video uploads
- Use MP4 with H.264 video + AAC audio for broad compatibility.
- Keep duration under 144 seconds; shorter for algorithmic favor.
- Target 1280 x 720 minimum; 1920 x 1080 for HD.
- Choose 16:9, 9:16, 1:1, or 2:1 based on audience intent.
- Add captions in SRT or VTT and verify timing.
- Ensure file size under platform limits and test uploads on off-peak hours if large.
Frequently asked questions
Below are concise answers to common questions about Twitter video requirements.
| Question | Answer | Why it matters |
|---|---|---|
| Can I upload AVI or MOV? | Yes, but MP4 is recommended for fewer processing issues. | Reduces re-encode delays and audio sync risks. |
| What’s the ideal length for engagement? | 15–90 seconds for strong completion; under 144 seconds supported. | Balances detail with retention and platform limits. |
| Are square or vertical videos okay? | Yes; 1:1 and 9:16 are supported and suit mobile feeds. | Choose based on where your audience watches primarily. |
| Do captions affect reach? | They improve accessibility and searchability, aiding reach. | Text-indexing helps discovery and honors audience preferences. |