-vf fps=24 turns 30 fps into 24 by dropping one frame in five, keeping the length and audio sync; -r 24 before -i stretches an 11-second clip past 13 seconds. On ReelSDK the fps version cost under half a cent, at $0.02 per compute minute.

Change the frame rate of a video with ffmpeg

Going from 30 to 60 fps with fps=60 only repeats frames, while minterpolate draws new ones but took about 5 times as long. ReelSDK's API runs the fps filter as is, billed by the second.

GuidesUpdated

24fps
ffmpeg -i input.mp4 -vf fps=24 -c:a copy output-24fps.mp4

The fps filter drops or repeats frames to hit the new rate and keeps the timing, so the copied audio still lines up. At 24 fps a 30 fps clip keeps its length with a fifth of its frames gone.

Variations

The other commands you will need

  1. Check the frame rate

    ffprobe prints the stream's frame rate and frame count. Our input printed 30/1,30/1,320.

    check
    ffprobe -v error -select_streams v:0 \
      -show_entries stream=r_frame_rate,avg_frame_rate,nb_frames \
      -of csv=p=0 input.mp4
  2. Use -r after the input

    As an output option, -r 24 also converts the rate, with slightly different rounding: it kept 2 more frames than the filter, so the video ran a little long.

    r24
    ffmpeg -i input.mp4 -r 24 -c:a copy r24.mp4
  3. Go up to 60 fps

    fps=60 shows every frame twice, so motion looks the same as before. minterpolate builds new in-between frames from motion estimates instead, and took about 5 times as long.

    60fps
    ffmpeg -i input.mp4 -vf fps=60 -c:a copy dup60.mp4
    ffmpeg -i input.mp4 -vf "minterpolate=fps=60:mi_mode=mci" \
      -c:a copy smooth60.mp4

The flags

The flags in these commands

The flags in these commands
FlagWhat it doesUsed here
-vf fps=24Drops or repeats frames to reach a constant 24 fps24 fps
-r 24 after -iSets the output rate; frames are dropped or repeated to fit-r
-r 24 before -iReads the input as if it were 24 fps, which changes its speedAvoid
minterpolate=fps=60Makes new in-between frames to reach 60 fps60 fps
mi_mode=mciMotion-compensated interpolation; dup repeats and blend mixes frames60 fps
-c:a copyCopies the audio; the length doesn't change, so it stays in syncAll

Sources: ffmpeg filters: fps, ffmpeg filters: minterpolate, ffmpeg documentation, checked November 2026.

The -r mistake that slows the video down

Where -r sits matters. After -i it sets the output rate. Before -i it tells ffmpeg to read the input as 24 fps, so nothing is dropped: every frame plays at the slower rate. Our test came out with over 13 seconds of video against 11 of audio, out of sync from the first second.

Use that on purpose only for slow motion without sound. To change the rate and keep the speed, use the fps filter.

Duplicate or interpolate

Raising the frame rate can't add motion that wasn't filmed. fps=60 repeats each frame, which makes a valid 60 fps file for a platform or an editor that wants one, with no change in how it looks.

minterpolate with mi_mode=mci estimates motion between frames and draws new ones in between. It is slow, about two and a half minutes for our 11-second clip, and the output came out 3 frames short. At a hard cut it would smear two shots together, so its scene-change detection, on by default, repeats a frame there instead.

A lower frame rate isn't a smaller file

Dropping frames didn't shrink our file. Both encodes used libx264 at its default CRF 23: the 24 fps output came out about 2% bigger than a 30 fps re-encode of the same clip, because each 24 fps frame got more bits. To control the size, use the CRF guide or set the bitrate.

Without installing ffmpeg

The same command as one API call

Send the same args to POST /v1/ffmpeg with the video's URL in inputs. Each job runs ffmpeg 8.1 on a fresh machine at $0.02 per compute minute, billed per second; this one finished in about 13 seconds, download and upload included, and cost under half a cent.

terminalTry it
curl "https://api.reelsdk.com/v1/ffmpeg?wait=60" \
  -H "Authorization: Bearer $REELSDK_KEY" \
  --json '{
    "inputs": {
      "input.mp4": "https://api.reelsdk.com/f/lib/demo/clip.mp4"
    },
    "args": ["-i", "input.mp4", "-vf", "fps=24", "-c:a", "copy", "output-24fps.mp4"],
    "outputs": ["output-24fps.mp4"]
  }'
output-24fps.mp4 from the API: 24 fps at the original length, about 4.4 MB.Input: clip.mp4

FAQ

Questions, answered

How do I change 30 fps to 24 fps with ffmpeg?

Use ffmpeg -i input.mp4 -vf fps=24 -c:a copy output.mp4. Our 30 fps clip came out at 24 fps with a fifth of its frames dropped and kept its length.

What is the difference between -r and -vf fps in ffmpeg?

After -i, both convert the rate; in our test -r 24 kept a couple more frames than the fps filter. Before -i, -r changes how the input is read: our 11-second video stretched to over 13 seconds while the audio kept its length.

How do I convert a video to 60 fps with ffmpeg?

-vf fps=60 repeats frames and is quick. -vf "minterpolate=fps=60:mi_mode=mci" draws new frames from motion and took about 5 times as long on our clip.

Can I change the frame rate with an API?

Yes. Send the same args to POST https://api.reelsdk.com/v1/ffmpeg with the video's URL in inputs. It runs ffmpeg 8.1 on a fresh machine per job for $0.02 per compute minute, billed per second, and failed jobs are free.

Ready to build?

Ship video from your app today

Your first $0.50 is free, and one key covers every endpoint.

Moonlit lake with a lit cabin under the mountains