ReelSDK vs FFmpegKit: $0.96 per 1,000 clips vs a DIY build
An ffmpeg-kit alternative now that its binaries are gone: ffmpeg 8.1 at $0.02 a minute
ReelSDK runs the commands your app passed to FFmpegKit on a server, for $0.02 per compute minute: compressing an 11-second 1080x1920 phone clip to 720x1280 takes about 6 seconds end to end and costs under a tenth of a cent. FFmpegKit itself was retired on 6 January 2025, its 6.0 binaries were pulled on 1 April 2025 and the repo was archived on 2 July 2026, so builds that download them fail: the CocoaPods zip and the Maven Central AARs now return 404.
- ReelSDK ffmpeg, billed by the second$0.96
- FFmpegKitNext or your own build, on the phone$0 + build and upkeep
ReelSDK from a measured run of the same clip: about 3 s of compute at $0.02 a minute. On-device encoding costs nothing per clip, but you compile, sign and ship FFmpeg yourself.
Which one to pick
Pick ReelSDK if
- Your iOS or Android build broke when the FFmpegKit binaries were removed, and you don't want to compile FFmpeg for every platform yourself
- You want ffmpeg 8.1 with the same arguments from Flutter, React Native, Swift or Kotlin, through your backend, with no native libraries in the app
- You want results as download URLs or signed webhooks with up to 6 attempts over about 7 hours, and jobs up to 10 minutes on server CPUs
Pick FFmpegKit if
- The video must be processed offline or must never leave the phone
- You can build FFmpegKitNext from source or maintain a fork, and you're fine with LGPL or GPL obligations in your app
- You need per-frame work in the UI, like scrubbing or thumbnails while the user edits, where a network round trip is too slow
Price per minute
Ways to replace FFmpegKit, and what they cost
On the phone, FFmpeg itself is free; what it costs is the build, the app size and the upkeep. ReelSDK bills raw ffmpeg at $0.02 per compute minute, by the second, with failed jobs free; the pricing page has every job type. The clip is an 11-second 1080x1920 video compressed to 720x1280 with libx264.
| Option | What it costs | 1,000 clips like this |
|---|---|---|
| FFmpegKit 6.0 packages | Free, but the binaries were removed in 2025 and the packages are deprecated | Not installable |
| FFmpegKitNext or your own FFmpeg build | Free source; you build, sign and ship binaries for each platform and keep them patched | $0 per clip |
| Platform APIs: AVFoundation, Media3 Transformer | Free in the OS SDKs; separate code for iOS and Android, no ffmpeg commands | $0 per clip |
| ReelSDK ffmpeg | $0.02 per compute minute; this clip took 2.9 s | $0.96 |
Community forks of the FFmpegKit packages exist on npm and pub.dev; check who maintains them and which FFmpeg they ship before you depend on one. Prices from Saying Goodbye to FFmpegKit, checked November 2026.
Head to head
ReelSDK and FFmpegKit, feature by feature
| ReelSDK | FFmpegKit | |
|---|---|---|
| Status | Maintained, ffmpeg 8.1 | Retired 6 January 2025; repo archived 2 July 2026 |
| Last release | Updated with the API | v6.0, react.native.v6.0.2 and flutter.v6.0.3, all from 18 September 2023 |
| Install | Nothing in the app; HTTPS from your backend | Binaries removed; npm package deprecated, Flutter package discontinued |
| Where it runs | Our servers | On the phone |
| Offline | No, needs a connection and an upload | Yes |
| App size | Nothing added | FFmpeg libraries for every architecture you ship |
| License | Pay per use | LGPL-3.0, or GPL-3.0 with the gpl packages that include libx264 |
| Limits | Inputs up to 500 MB each and 1 GB per job, by URL or upload; 10 minutes per job | The phone's CPU, memory and battery |
| Results | Download URLs valid 7 days, or a signed webhook | A file on the device |
Be honest
Where FFmpegKit is the better choice
Offline and private
FFmpegKit ran on the device, so video never left the phone and the app worked without a connection. Any server API, ReelSDK included, needs the clip uploaded first.
No per-clip cost, no upload
On-device encoding uses the phone's CPU, so a million clips cost you nothing, and users on slow mobile data skip uploading the full file before it is compressed.
Interactive editing
Scrubbing a timeline, drawing thumbnails while the user trims, or previewing a filter needs answers in milliseconds. That is work for the device; a round trip to a server is too slow.
Migration
Moving a render from FFmpegKit
Move the command from FFmpegKit.execute() to the args of POST /v1/ffmpeg, called from your backend so the API key never ships inside the app. With the request below, the clip came back as a 1.1 MB 720x1280 mp4 in about 6 seconds and cost under a tenth of a cent. See the output. App-side guides: React Native and Flutter.
FFmpegKit today
import { FFmpegKit, ReturnCode } from "ffmpeg-kit-react-native";
// On-device compression; libx264 needs one of the -gpl packages, whose binaries are gone
const session = await FFmpegKit.execute(
"-i input.mp4 -vf scale=-2:1280 -c:v libx264 -preset veryfast -crf 28 " +
"-c:a aac -b:a 128k -movflags +faststart output.mp4"
);
if (ReturnCode.isSuccess(await session.getReturnCode())) {
// output.mp4 is ready on the device
}
The same render on ReelSDK
// On your backend: take the clip from the app, then POST /v1/uploads?filename=clip.mp4
// with the raw bytes returns its URL. This run used a hosted sample instead.
const res = await fetch("https://api.reelsdk.com/v1/ffmpeg?wait=60", {
method: "POST",
headers: { Authorization: `Bearer ${process.env.REELSDK_KEY}`, "Content-Type": "application/json" },
body: JSON.stringify({
"inputs": {
"in.mp4": "https://api.reelsdk.com/f/lib/demo/clip.mp4"
},
"args": [
"-i", "in.mp4", "-vf", "scale=-2:1280", "-c:v", "libx264", "-preset",
"veryfast", "-crf", "28", "-c:a", "aac", "-b:a", "128k", "-movflags",
"+faststart", "out.mp4"
],
"outputs": ["out.mp4"]
}),
});
const { job } = await res.json();
// 200 OK after 5.7 s, trimmed
// {
// "job": {
// "id": "job_a3z2an2bbyq2xg987ctf",
// "op": "ffmpeg",
// "status": "succeeded",
// "duration_s": 10.678,
// "outputs": { "out.mp4": "https://api.reelsdk.com/f/out/job_a3z2an2bbyq2xg987ctf/out.mp4?s=..." }
// }
// }Field by field
| FFmpegKit | ReelSDK |
|---|---|
FFmpegKit.execute(command) | args: the same command split into an array |
input.mp4 on the device | inputs: a URL, from POST /v1/uploads for files from the app |
output.mp4 on the device | outputs: names you want back, as download URLs |
ReturnCode.isSuccess() | job.status is succeeded, or error.code says why not |
executeAsync() with callbacks | A webhook, or GET /v1/jobs/{id} |
-gpl packages for libx264 | libx264 is included |
FAQ
ReelSDK vs FFmpegKit, answered
Why did FFmpegKit stop working?
Its maintainer retired the project on 6 January 2025 and removed the native binaries from the package hosts: versions before 6.0 on 1 February 2025 and 6.0 on 1 April 2025. Builds that download them now fail: the CocoaPods zip and the Android AARs on Maven Central return 404. The GitHub repo was archived on 2 July 2026.
Is there an official replacement for FFmpegKit?
The maintainer started FFmpegKitNext, a source-only continuation: you build the binaries yourself. Community forks also publish packages on npm and pub.dev. If you'd rather not ship FFmpeg in the app at all, ReelSDK runs the same commands on a server.
Can I call ReelSDK straight from a Flutter or React Native app?
Call it from your backend instead, so the API key never ships inside the app. The app uploads the clip to your server or passes a URL, your server calls POST /v1/ffmpeg and returns the download URL. Single uploads take up to 100 MiB and multipart uploads up to 5 GB.
How much does it cost to compress a video with ReelSDK?
Raw ffmpeg jobs cost $0.02 per compute minute, billed by the second, and failed jobs are free. Compressing an 11-second 1080x1920 clip took 2.9 seconds of compute, under a tenth of a cent, so 1,000 clips cost about $0.96.
Other comparisons
Ready to build?
Ship video from your app today
Your first $0.50 is free, and one key covers every endpoint.
