Frame rate and motion
60 fps video hosting.
Your frame rate and your bitrate, kept as exported.
A 60 fps file carries twice as many frames per second as a 30 fps file, so at the same bitrate each frame gets half the data. Platforms that re-encode decide that budget for you. Here nothing re-encodes: the file plays at the frame rate and bitrate you exported. Whether it plays smoothly is then decided by the viewer's decoder and connection, and this page is plain about both.
Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month
By uncompressed.io · Updated September 2026
Start with the arithmetic
Doubling the frame rate
halves the data in each frame.
Bitrate is bits per second. Divide it by frames per second and you get the budget each frame is encoded with. Motion is exactly where that budget runs out first, which is why 60 fps footage falls apart sooner than 24 or 30 fps footage at the same number.
Per-frame figures are arithmetic (megabits per second divided by 60), not measurements. Real encoders spend more on busy frames and less on calm ones. Vimeo and YouTube figures from their own help pages, fetched 18 September 2026.
Vimeo publishes 7 Mbps as the maximum video bitrate for its 1080p 60fps rendition, and says the listed bitrates are a maximum, so a video could transcode lower depending on the picture. At 60 frames that is about 117 kilobits per frame at most. YouTube does not publish what it plays back, but its own upload guidance shows it knows frame rate costs bits: for 1080p SDR it recommends 8 Mbps at standard frame rates and 12 Mbps at 48, 50 or 60 fps. For 2160p the recommendation moves from 35 to 45 Mbps up to 53 to 68 Mbps.
One more line on the Vimeo page is worth reading if 60 fps matters to you. Only its 1080p, 2K and 4K rungs are labelled with 60fps; the 240p to 720p rungs are not, and the page states, “Generally, we transcode to 30fps unless otherwise noted.” If a viewer’s player steps down a rung, check what frame rate that rung carries.
What to export
Starting bitrates
for a 60 fps master.
These are the ranges we give members for 60 fps exports. They sit well above the delivery maximums platforms publish, because here the export is the file the viewer receives. Content decides where in the range you land.
Our recommended export ranges. We give no H.264 figure for 4K at 60 fps; use HEVC there. Export at the timeline's own frame rate, at one constant rate, and never upscale.
Match the shoot
Keep the timeline at the rate the footage was recorded. YouTube's guidance says the same for its uploads: encode at the frame rate the content was recorded. 59.94 and 60 are different rates; pick the one your camera used.
Choose the codec for the viewer
For broad browser compatibility, use H.264. HEVC playback depends on the viewer's device, so test it before you rely on it. For 4K at 60 fps we list HEVC only.
Pick the bitrate for the motion
Start in the middle of the range. Move up for water, foliage, grain, confetti or a fast pan, where 60 fps spends its bits; move down for an interview or a screen recording.
Upload and test on their machine
Send the link to the reviewer before the deadline and ask them to play the busiest shot. One test answers both open questions, decoder and connection, for the only setup that matters.
What happens to the file here
It stays at 60 fps,
and it stays at your bitrate.
Browser playback uses your uploaded export without another platform re-encode. Codec, device and connection requirements still apply.
No frame-rate cap or conform
The upload is checked for size, not for frame rate. Nothing reads the rate to change it, and with no transcode step there is nothing that could. A 60 fps file stays 60 fps; a 59.94 file stays 59.94.
No bitrate ladder
The player is a single video element pointed at your stored file. There is no manifest and no set of renditions. A 48 Mbps 1080p60 export is served at its own bitrate, connection permitting.
No lower rendition to fall back to
If the viewer's connection cannot hold the rate, the player buffers instead of quietly switching to a smaller, lower frame rate copy. For a client judging motion, a visible pause is the more honest failure.
No promise about their device
Decoding 60 frames a second is real work, and it rises with resolution and codec. Apple itself notes that 1080p or lower and 60 fps or lower are more broadly compatible with older devices. We make no smooth-playback promise for any device; we tell you to test.
48 Mbps
Top of our 1080p60 HEVC range
Served at that rate here. Vimeo's published maximum for 1080p 60fps is 7 Mbps.
6 MB/s
Sustained connection needed
Arithmetic from the bitrate. The viewer's line has to hold it for the whole runtime.
21.6 GB
One hour at that rate
Decimal gigabytes, before audio and container overhead.
The caveat that travels with every claim
When this is the wrong tool
When
you should stay on YouTube or Vimeo.
Full-bitrate 60 fps is the right choice for a small, known audience: a client signing off a sports edit, an agency reviewing a product spot, a director checking a fast pan on a good machine. It is the wrong choice for a large public on phones and mobile networks.
Stay with a laddered platform when you need a 60 fps video to reach thousands of strangers. A ladder exists to serve viewers whose connection you cannot predict, and a smaller copy that keeps playing beats a perfect file that buffers. Gameplay channels and public marketing videos belong there. Use this for the review copy and the delivery master, and publish the public cut wherever it reaches the most people. If the only thing you need is more headroom than a platform allows, the no bitrate limit guide sets out what that does and does not buy.
Questions
Frequently asked
Does uncompressed.io convert 60 fps video to 30 fps?
No. There is no transcode step, so nothing here changes the frame rate. The upload is not checked or conformed for frame rate either: the file keeps the cadence it was exported at. Smooth playback still depends on the viewer's decoder and connection.
Should I export at 59.94 or 60?
Export at the rate of your timeline, which should match how the footage was shot. HandBrake's documentation lists 29.97/59.94 or 30/60 as the North American broadcast rates and 25/50 as the European ones, and YouTube tells uploaders to encode at the frame rate the content was recorded. We keep whichever you deliver.
What bitrate should a 1080p60 export use?
Our starting range for 1080p at 60 fps is 24 to 48 Mbps in HEVC and 32 to 64 Mbps in H.264. Content decides where you land: an interview sits low, water, foliage or a fast pan sits high. For comparison, YouTube's recommended upload bitrate for 1080p SDR rises from 8 Mbps at standard frame rates to 12 Mbps at 48, 50 or 60 fps.
What happens if the viewer's connection cannot keep up?
The player buffers. There is one file, yours, and no lower rendition or lower frame rate to switch down to. A laddered platform can hand a struggling viewer a smaller copy; we cannot, which is the trade for never re-encoding.
Send the 60 fps master you actually exported
Upload your export and it is served as uploaded: same frame rate, same bitrate, no re-encode on our side. Test it on your client's machine before the review, then pick a plan when you need room for more films.
Sources
- 1.Vimeo Help Center, Guidelines for determining playback resolution: 1080p 60fps maximum video bitrate 7 Mbps; 4K (30fps and 60fps) 22 Mbps; bitrates are a maximum (fetched 18 September 2026)
- 2.YouTube Help, Recommended upload encoding settings: same frame rate as recorded; high frame rate bitrates for SDR and HDR (fetched 18 September 2026)
- 3.Apple Support, Using HEIF or HEVC media on Apple devices: 1080p or lower and 60 fps or lower are more broadly compatible with older devices (fetched 18 September 2026)
- 4.HandBrake documentation, Frame rates: common frame rates for film and broadcast (fetched 18 September 2026)