About this tool
Upload a video and convert its frame rate to any target FPS — 23.976, 24, 25, 29.97, 30, 48, 50, 60, 120 fps and more. Runs entirely in your browser via FFmpeg.wasm.
Frame Rate Converter re-encodes a video to a different frame rate in the browser using FFmpeg compiled to WebAssembly, applying the `fps` filter and writing an H.264 MP4 at CRF 18. Ten standard targets are offered — 23.976, 24, 25, 29.97, 30, 48, 50, 59.94, 60 and 120 fps — and the source rate is measured first by timing ten decoded frames, so you can see what you are converting from. It suits editors and creators who need a clip to match a timeline's rate without opening an NLE or uploading footage anywhere.
Open Frame Rate Converter on AltFTool — it loads instantly in your browser.
Press Select Video or drop a file on the upload area; the page reports its Frame Rate, Duration and Resolution.
Choose a Target Frame Rate from the ten options between 23.976 and 120 fps, then press Convert to N fps.
Download converted_<fps>fps.mp4, re-encoded with libx264 at CRF 18 in yuv420p.
The NTSC pull-down rates 23.976, 29.97 and 59.94 are selectable alongside 24, 25, 30, 48, 50, 60 and 120.
Frame timing is sampled over ten decoded frames via requestVideoFrameCallback, so you are not guessing what the file already is.
Output is H.264 at CRF 18 with yuv420p pixel format, a setting chosen for quality rather than the smallest file.
Ten: 23.976, 24, 25, 29.97, 30, 48, 50, 59.94, 60 and 120 fps. The list covers cinema (24), PAL (25 and 50), NTSC (23.976, 29.97, 59.94) and high-frame-rate capture.
No. The `fps` filter duplicates existing frames to reach a higher rate and drops frames to reach a lower one — it does not synthesise new in-between frames, so going from 30 to 60 fps adds file size without adding motion detail.
The video is re-encoded, so it is not a lossless copy, but it is encoded with libx264 at CRF 18 — a setting generally treated as visually lossless for most footage. Converting the same file repeatedly will still compound generation loss.
No. FFmpeg runs as WebAssembly inside the page, so the file is read from disk into browser memory and the converted MP4 is produced locally. Large files are limited by your device's RAM rather than by an upload cap.
Add the Frame Rate Converter widget to your blog or website — free, responsive, no signup. Just keep the “Widget by AltFTool” credit link visible.
<iframe src="https://www.altftool.com/embed/widget/frame-rate-converter"
title="Frame Rate Converter — free AltFTool widget"
width="100%" height="640" style="border:0;border-radius:12px;overflow:hidden"
loading="lazy" referrerpolicy="no-referrer-when-downgrade" allow="clipboard-write"></iframe>
<p style="font-size:12px;margin:4px 0 0">Widget by <a href="https://www.altftool.com/tools/all/frame-rate-converter?utm_source=embed&utm_medium=widget" rel="nofollow">AltFTool — free online tools</a></p>