ReelSDK vs MoviePy: 18 s for $0.0075 vs 8 minutes free
A MoviePy alternative: the same 15-second slideshow in 18 seconds, not 8 minutes
At $0.03 per output minute, a 15-second slideshow costs three quarters of a cent on ReelSDK and comes back from one JSON request in about 18 seconds. MoviePy is free and flexible, but it builds every frame in Python, so the same slideshow with a slow zoom, crossfades and music took about 8 minutes on about one CPU.
- ReelSDK, request to finished video18 s
- MoviePy, best of two runs466 s
- MoviePy, second run533 s
Measured with the MoviePy script below on 2 CPUs of a shared host, where the Python process used about one CPU. A fast dedicated CPU will do better, but the frames are still built in Python.
Which one to pick
Pick ReelSDK if
- You want slideshows, captions or faceless shorts from a JSON request, rendered in seconds on our machines instead of minutes in a Python worker
- Your MoviePy 1.x code broke on 2.x, where moviepy.editor is gone, set_ became with_ and effects became classes, and you'd rather not port it
- You need captions transcribed and burned in, or an AI voiceover at $0.05 per 1,000 characters, without wiring up Whisper, a TTS service and font files
Pick MoviePy if
- You need frame-level control in Python: numpy on frames, masks, custom compositing, any effect you can write
- Everything must run locally or offline, with no price per video
- You edit a handful of videos in a notebook, where render time doesn't matter
Price per minute
MoviePy and ReelSDK, what the same slideshow costs
MoviePy is free under MIT, so the cost is the machine it runs on. ReelSDK bills slideshows at $0.03 per output minute, by the second, with transcription for captions included; the pricing page has every job type. The job is the 15-second slideshow above, priced from the roughly 8 minutes MoviePy took, with two renders at once on a 2 vCPU machine that stays busy.
| Option | What you pay | This slideshow | 1,000 a month |
|---|---|---|---|
| MoviePy on your own computer | Free | About 8 minutes of one CPU | About 130 CPU hours |
| MoviePy on a DigitalOcean 2 vCPU droplet | $0.0625 an hour | About 0.4 cents | About $4 |
| MoviePy on AWS EC2 c7i.large | $0.08925 an hour | About 0.6 cents | About $6 |
| ReelSDK slideshow | $0.03 per output minute | 0.75 cents | $7.50 |
Machine prices assume no idle time and leave out the worker, queue and storage around the script. On a faster CPU MoviePy costs less per video, so treat its figures as an upper bound. Prices from DigitalOcean droplet pricing, checked November 2026.
Head to head
ReelSDK and MoviePy, feature by feature
| ReelSDK | MoviePy | |
|---|---|---|
| This slideshow | About 18 seconds from request to video, for three quarters of a cent | About 8 and 9 minutes in two runs |
| What you write | One JSON body | A Python script: clips, effects, compositing, audio, export |
| Ken Burns and transitions | motion and transition options | Write them: resized() with a function of time, CrossFadeIn |
| Captions | Transcribed and burned in, inside the $0.03 per minute | TextClip with a font file; no transcription |
| Voiceover | Optional AI voice, $0.05 per 1,000 characters | Bring your own TTS |
| Runs on | Our machines | Your machine: Python, pillow, numpy and ffmpeg via imageio-ffmpeg |
| Version | A stable HTTP API | Latest release May 2025; 2.0 broke 1.x scripts |
| Limits | 500 MB per input, 15 minutes of media, 10 minutes per job | Your memory and CPU |
| License | Pay per use | MIT |
Be honest
Where MoviePy is the better choice
Any effect you can code
MoviePy hands you every frame as a numpy array, so masks, custom transitions, generated graphics and frame math are a few lines of Python. ReelSDK gives you set options and raw ffmpeg, not arbitrary Python per frame.
Free and local
MIT licensed, no account, no per-video price and no upload. For offline tools, notebooks or private footage, that beats any API.
Interactive editing
In a notebook you can preview a clip, tweak one effect and render again, which suits one-off edits and teaching. ReelSDK is built for repeatable jobs sent by code.
Migration
Moving a render from MoviePy
Swap the clip-building script for one JSON body: photos, size, seconds per photo, motion, transition and music. With the request below, the slideshow came back in about 18 seconds, for three quarters of a cent. See the output. The MoviePy script on the left took about 8 minutes to make the same video.
MoviePy today
from moviepy import AudioFileClip, CompositeVideoClip, ImageClip, concatenate_videoclips, vfx
PHOTOS = ["river", "plaza", "oranges", "flamenco", "tapas"]
SECONDS, FADE, ZOOM = 3.4, 0.5, 0.096
clips = []
for i, name in enumerate(PHOTOS):
still = ImageClip(f"{name}.jpg").with_duration(SECONDS).resized(height=1920)
moving = still.resized(lambda t: 1 + ZOOM * t / SECONDS)
frame = CompositeVideoClip([moving.with_position("center")], size=(1080, 1920)).with_duration(SECONDS)
if i > 0:
frame = frame.with_effects([vfx.CrossFadeIn(FADE)])
clips.append(frame)
video = concatenate_videoclips(clips, method="compose", padding=-FADE)
music = AudioFileClip("music.mp3").subclipped(0, video.duration).with_volume_scaled(0.3)
video.with_audio(music).write_videofile("slideshow.mp4", fps=30, codec="libx264", audio_codec="aac")
The same render on ReelSDK
curl "https://api.reelsdk.com/v1/slideshow?wait=60" \
-H "Authorization: Bearer $REELSDK_KEY" \
--json '{
"images": [
"https://api.reelsdk.com/f/lib/demo/seville/river.jpg",
"https://api.reelsdk.com/f/lib/demo/seville/plaza.jpg",
"https://api.reelsdk.com/f/lib/demo/seville/oranges.jpg",
"https://api.reelsdk.com/f/lib/demo/seville/flamenco.jpg",
"https://api.reelsdk.com/f/lib/demo/seville/tapas.jpg"
],
"size": "9:16",
"seconds_per_image": 3,
"motion": "kenburns",
"transition": "fade",
"music": {
"url": "https://api.reelsdk.com/f/lib/music/chill/calm-currents.mp3",
"volume": 0.3
}
}'
# 200 OK after 17.7 s, trimmed
# {
# "job": {
# "id": "job_ofta8fs87s1poybmnato",
# "op": "slideshow",
# "status": "succeeded",
# "duration_s": 15,
# "outputs": { "video": "https://api.reelsdk.com/f/out/job_ofta8fs87s1poybmnato/video.mp4?s=..." }
# }
# }Field by field
| MoviePy | ReelSDK |
|---|---|
ImageClip(path).with_duration(3.4) | images and seconds_per_image |
resized(lambda t: 1 + 0.096 * t / 3.4) | motion: kenburns |
vfx.CrossFadeIn(0.5) | transition: fade, 0.5 s by default |
AudioFileClip(...).with_volume_scaled(0.3) | music: { url, volume: 0.3 } |
write_videofile(fps=30, codec="libx264") | An H.264 mp4 at 30 fps |
TextClip(font=...) | captions: true with a voiceover, transcribed for you |
FAQ
ReelSDK vs MoviePy, answered
Why is MoviePy so slow?
It composes every frame as an image in Python and pipes the frames to ffmpeg, and its README says this is slower than using ffmpeg directly. Our 15-second slideshow with a slow zoom and crossfades took about 8 minutes with MoviePy on about one CPU, and nearly as long without the zoom, so most of the time goes to compositing.
Why did my MoviePy code break after upgrading?
MoviePy 2.0 changed the API: moviepy.editor is gone, set_ methods became with_, effects are classes applied with with_effects(), resize, crop and rotate became resized, cropped and rotated, and TextClip needs a font file path. ImageMagick, PyGame, OpenCV and scipy were dropped.
Is MoviePy free for commercial use?
Yes, MoviePy is MIT licensed. You pay for the machine: 1,000 of these slideshows take about 130 CPU hours, about $4 to $6 on a busy 2 vCPU cloud machine. ReelSDK charges $7.50 for the same 1,000 at $0.03 per output minute.
Can ReelSDK add captions and a voiceover?
Yes. Add a voiceover, either your own audio file or AI speech from text at $0.05 per 1,000 characters, and set captions to true: the voiceover is transcribed and burned in at no extra cost.
Other comparisons
Sources, checked November 2026
Ready to build?
Ship video from your app today
Your first $0.50 is free, and one key covers every endpoint.
