OpenMock BlogVideo specs by platform
X (Twitter) video specs and a 15-second product demo format
X video specs for 2026 — 1920×1080, 16:9 or 9:16, under 140 seconds, MP4 H.264 — plus how to make a device-mockup demo that stops the scroll.
X is where indie makers launch. It is also a feed that autoplays muted at phone width, so a product demo has about one second to read as something is happening on a screen before the thumb moves on. A 3D device with a screen recording playing on it and a slow camera move does that job better than a raw screen capture ever will.
X (Twitter) video specs (September 2026)
| Recommended size | 1920 × 1080 (16:9) or 1080 × 1920 (9:16); 1:1 also supported |
| Maximum resolution | 1920 × 1200 — 4K uploads are downscaled server-side |
| Length | Up to 140 seconds for standard accounts; longer for Premium subscribers |
| File size | Up to 512 MB (standard) |
| Format | MP4 or MOV, H.264 video, AAC audio |
| Frame rate | Up to 60 fps accepted; 30 fps is the safe default |
Because X re-encodes everything, export clean and let the platform compress: 1080p H.264 at a high bitrate survives the second encode far better than a file that is already squeezed.
The export settings that fit X (Twitter)
Export 1920 × 1080 for a tweet that is mostly viewed on desktop or embedded elsewhere, and 1080 × 1920 (9:16) when your audience is mobile-first — vertical video fills the phone screen and gets more of the timeline. Keep the clip between 8 and 20 seconds; X shows a progress bar and people finish short videos. Set motion blur to low so UI text on the device stays legible after X's compression.
A X (Twitter) demo that people actually watch
- Open on the screen already doing the thing — no logo card, no fade from black
- Put the tagline in a text shot inside the video; muted autoplay means the tweet text is not seen at the same time as the video
- One camera move per clip: a slow push-in or a gentle orbit, not both
- Loop-friendly: end near where you started so the autoplay repeat does not jump
- Post the same clip as a native upload, not a link — native video gets the autoplay
Making it in OpenMock
- Open OpenMock in a desktop browser and set the canvas ratio to 16:9 in the top bar.
- Pick a device (or the frameless screen) and drop your screenshot or screen recording onto it.
- Keyframe a single 8–12 second camera move — a push-in on the device while the screen recording plays.
- Add a text shot for the hook and a logo shot at the end if you want a branded close; both are shots on the same timeline.
- Export video with the 16:9 — 1920×1080 (1080p) preset at 30 or 60 fps. Free exports are 720p/30 fps with a watermark; Pro gives you the full-resolution, watermark-free file.
FAQ
What aspect ratio should a X (Twitter) product video be?
Use 16:9 (1920 × 1080) for a desktop-leaning audience and embeds; use 9:16 (1080 × 1920) when most viewers are on phones. Both are native on X. Avoid 4K — X downscales to a maximum of 1920 × 1200 anyway.
How long should a X (Twitter) app demo be?
Eight to twenty seconds. Standard accounts can post up to 140 seconds, but completion rate and the autoplay loop both favour short clips that show one thing.
Should I upload 4K video to X?
No. X caps output at 1920 × 1200 and re-encodes uploads; a clean 1080p H.264 export at high bitrate looks better after X's compression than a 4K file that gets downscaled.
Specs checked against public X media guidelines and current help-center limits on September 4, 2026. Platforms change limits without notice — re-check before a big launch.