X Video Frame Rate Limit: Is It 40 fps or 60 fps?

X publishes two different maximum frame rates for video, and both of them are official. The help center's web-upload FAQ lists "Maximum frame rate: 40 fps". The developer documentation says frame rate "must be 60 FPS or less". Each block states a single figure and neither mentions the other's.

That matters because 40 is a strange ceiling, and it is scoped narrowly: it appears in one help center FAQ answer, under a question that asks specifically about videos uploaded on the web. The 60 FPS figure comes from a different document covering a different upload route.

The frame rate numbers, at a glance

Every cell above is quoted from a page X publishes. There is no consensus figure to give you, because X has not published one.

Where the 40 fps figure comes from

The help center FAQ headed "What are the limitations on video resolutions and aspect ratios that can be uploaded on the web?" answers with this block:

Minimum resolution: 32 x 32
Maximum resolution: 1920 x 1200 (and 1200 x 1900)
Aspect ratios: 1:2.39 - 2.39:1 range (inclusive)
Maximum frame rate: 40 fps
Maximum bitrate: 25 Mbps

Read the qualifier in the question, not just the numbers: this block is scoped to uploads made on the web. That single word is the reason the block can coexist with a different set of numbers in the developer documentation without either one being wrong.

The developer docs disagree on three of four items

The API media best practices page states, under "Advanced":

• "Frame rate: must be 60 FPS or less"
• "Dimensions: must be between 32x32 and 1280x1024"
• "Aspect ratio: must be between 1:3 and 3:1"

Line the two blocks up and the conflict is not a rounding difference:

Three of the four shared rows conflict, and they do not conflict in a consistent direction: the help center allows a much larger frame, while the developer docs allow a higher frame rate and more extreme aspect ratios. Only the 32 x 32 minimum matches.

So do not average them, and do not treat either set as "X's video specs". Pick the page that matches how you are uploading, and check the current values in the official documentation before you build an export preset around them.

What to do if your footage is 60 fps

If you want one number that sits inside every published ceiling, 30 fps is it — it is below 40 and below 60, and the developer docs list 30 FPS as one of two recommended frame rates (the other being 60 FPS).

If you want to keep 60 fps, the thing to watch is bitrate rather than the frame count itself. High frame rate exports carry more data per second, and the web-upload block above caps bitrate at 25 Mbps. X's own advice for uploads that fail is blunt about this: "Even if your file is under our maximum size, we may still have issues ingesting the file. Reducing the size of the file reduces the time of the upload, maximizing your chances for success." The suggested method on that page is to reduce the bitrate and re-export.

This runs inside your browser tab — the file is read from disk, re-encoded locally and handed back, never uploaded to a server. It outputs H.264 in an MP4 container, which lines up with the developer docs' recommended "Video Codec: H264 High Profile". For reference points on bitrate, the Media Studio encoding block recommends "5-8 mbps", while the developer page states a "Minimum Video Bitrate: 5,000 kbps" and separately publishes an upload recommendation table putting 1280x720 at 2048K — the same page gives both, and labels the table "not a requirement".

Gotchas worth knowing before you re-export

Media Studio's numbers are fenced off by X itself. Its spec section opens with: "These instructions are only valid for Media Studio, and should not be followed for usage of the X developer API, Pro Media API, desktop upload, or mobile upload." So its 60 FPS ceiling does not settle the question for a normal web upload.

Frame rate is on X's own failure checklist. The X Ads upload troubleshooting page asks: "Confirm your video is within our required specifications. Does your video file have the correct video and audio codecs? the right frame rate? is your file too large?" Frame rate is listed alongside codec and size as a reason ingestion fails.

Interlaced sources are a separate problem. The developer docs' hard constraints include "Must use progressive scan", "Only YUV 4:2:0 is supported", "Must not have open GOP", and audio that is "mono or stereo, not 5.1 or greater". A 60i camera file can satisfy a frame rate ceiling and still fall foul of the scan-type rule.

Livestreaming is a third rulebook. For RTMP, the ads creative specs list 30 fps recommended and 60 fps maximum, and the Live Studio page publishes keyframe guidance tied directly to frame rate:

24 fps -> 72 frames
30 fps -> 90 frames
50 fps -> 150 frames
60 fps -> 180 frames

FAQ

What is the maximum frame rate for video on X? There are two published answers. The help center's web-upload FAQ says "Maximum frame rate: 40 fps"; the developer documentation says frame rate "must be 60 FPS or less". The two are scoped to different upload routes, so check the official documentation for the route you are actually using.

Can I upload 60 fps video to X? 60 FPS is within the developer docs' stated ceiling and is one of the two frame rates that page recommends. It is above the 40 fps figure the help center gives for web uploads. X's documentation does not state what happens to a file that exceeds a stated ceiling, so do not treat either page as a guarantee.

Does X support 120 fps or 240 fps video? Both published ceilings — 40 fps and 60 FPS — are well below 120, and no official page states a higher figure or describes how high frame rate footage is handled. Check the official documentation rather than assuming.

Will X convert my 60 fps video to 30 fps? X does not publish the parameters of its server-side processing. What it does say is that "All uploads are processed for optimization across multiple platforms", and that it may "modify or adapt your original video for distribution, syndication, publication, or broadcast", including "modifying the resolution and bitrate of the original video while streaming based on the speed and stability of the viewer's internet connection". Frame rate is not named in either statement.

My frame rate is fine and the upload still failed. What else should I check? X's Media Studio page attributes "Upload failed" to "file size, resolution, encoding settings, or a connection issue". The developer docs add the hard constraints listed above — progressive scan, YUV 4:2:0, 1:1 pixel aspect ratio, AAC LC audio, no open GOP. Any one of those can reject a file that is comfortably inside every size and duration limit.

Frame rate is one of several X video numbers that differ depending on which official page you land on. For the rest of the platform-limit write-ups, see the limits hub; for re-exports that only need a smaller file rather than a different frame rate, compress video handles it locally, and if your source is a QuickTime file, MOV to MP4 converts the container first. The full set is on the Clapr tools page. Platform specs for other networks are collected in posts like Instagram Reels resolution requirements.

All figures quoted from X's help center, developer documentation, and business help pages, checked 16 September 2026. X's pages disagree with each other on several of these values — verify against the official page that covers your upload route before relying on them.