Migrate from Bitmovin to ChangeThisFile

Bitmovin is built for the streaming industry: adaptive bitrate encoding, HLS/DASH packaging, DRM integration, per-title encoding optimization, and CDN delivery. These are the capabilities that power video-on-demand platforms. If that's what you need, Bitmovin earns its cost.

But there's a subset of Bitmovin customers who adopted it for a simpler use case — converting uploaded videos between formats for download or playback — and are paying enterprise pricing for features they don't use. For that use case, ChangeThisFile is a direct API with no encoding pipeline to configure.

This guide is direct about the tradeoffs: most Bitmovin customers should stay on Bitmovin. A narrow set should consider migrating.

Who should consider migrating (and who definitely shouldn't)

Consider migrating if:

• You use Bitmovin only for MP4↔WebM, MOV→MP4, AVI→MP4, or similar format swaps
• Your use case is file download, not streaming playback
• You don't use HLS/DASH outputs, DRM, or multi-bitrate ladders
• You're on Bitmovin's developer/trial tier and the cost exceeds the value
• Video quality settings (specific bitrate, resolution, codec) are not critical — FFmpeg defaults are acceptable

Do NOT migrate if:

• You generate HLS or DASH manifests for adaptive streaming
• You use Bitmovin's DRM integration (Widevine, PlayReady, FairPlay)
• You need multi-bitrate rendition ladders (360p/720p/1080p/4K)
• You need per-title encoding optimization
• You use Bitmovin's player SDK
• You need cloud-based encoding at scale with GPU acceleration
• Your customers are streaming video in a player — ChangeThisFile produces files, not streams

ChangeThisFile uses FFmpeg with standard settings. Bitmovin's encoding pipeline is purpose-built for streaming delivery and offers control that FFmpeg's defaults don't match.

Cost comparison for simple conversion use cases

Bitmovin's pricing is based on encoded minutes, not conversion count. Short clips are cheap; long videos or high-resolution encoding can be expensive per-job. ChangeThisFile charges per conversion regardless of file length or resolution. For short-clip conversion at low volume, the savings are immediate and large.

Important caveat: These savings only apply if simple format conversion is genuinely your use case. If you need streaming delivery, the comparison isn't meaningful — ChangeThisFile can't replace Bitmovin's streaming pipeline at any price.

API approach comparison

The architectural difference is fundamental: Bitmovin is a pipeline system for professional encoding; ChangeThisFile is a file conversion endpoint. For simple use cases, the pipeline reduces to a single HTTP call.

Code migration: BEFORE and AFTER

# BEFORE: Bitmovin (pipeline setup + polling)
import bitmovin_api_sdk as bm
import time

client = bm.BitmovinApi(api_key='your_bitmovin_key')

# Create encoding
encoding = client.encoding.encodings.create(bm.Encoding(name='mp4-to-webm'))

# Add input (HTTP source)
http_input = client.encoding.inputs.http.create(
    bm.HttpInput(host='your-storage.com')
)
stream_input = bm.StreamInput(
    input_id=http_input.id,
    input_path='/videos/source.mp4'
)

# Configure VP9 codec
vp9 = client.encoding.configurations.video.vp9.create(
    bm.Vp9VideoConfiguration(name='vp9-720p', width=1280, height=720)
)

# Add stream
stream = client.encoding.encodings.streams.create(
    encoding_id=encoding.id,
    stream=bm.Stream(codec_configuration_id=vp9.id, inputs=[stream_input])
)

# Add WebM muxing + output
output = client.encoding.outputs.s3.create(
    bm.S3Output(bucket_name='my-bucket', access_key='...', secret_key='...')
)
muxing = client.encoding.encodings.muxings.webm.create(
    encoding_id=encoding.id,
    webm_muxing=bm.WebmMuxing(
        streams=[bm.MuxingStream(stream_id=stream.id)],
        outputs=[bm.EncodingOutput(output_id=output.id, output_path='/output/')]
    )
)

# Start + poll
client.encoding.encodings.start(encoding_id=encoding.id)
while True:
    status = client.encoding.encodings.status(encoding_id=encoding.id)
    if status.status == bm.Status.FINISHED:
        break
    if status.status == bm.Status.ERROR:
        raise Exception('Encoding failed')
    time.sleep(5)

# AFTER: ChangeThisFile (one call, download result)
import requests

response = requests.post(
    'https://changethisfile.com/v1/convert',
    headers={'Authorization': 'Bearer ctf_sk_your_key'},
    files={'file': open('source.mp4', 'rb')},
    data={'target': 'webm'}
)
with open('output.webm', 'wb') as f:
    f.write(response.content)

The Bitmovin version is ~50 lines of pipeline configuration. The ChangeThisFile version is 8 lines. The tradeoff: Bitmovin gives you precise codec control, GPU-accelerated encoding, and cloud-native S3 integration. ChangeThisFile gives you simplicity.

Auth and setup migration

1. Get your CTF key: changethisfile.com/v1/keys/free. Free tier: 1,000 conversions/month.
2. Uninstall the Bitmovin SDK: Remove bitmovin-api-sdk from your requirements. ChangeThisFile needs no SDK — any HTTP client works.
3. Remove encoding pipeline setup code: The Input, Codec, Stream, Muxing, Output resource creation code is all eliminated. The "encoding" is just a single POST.
4. Handle file download: Bitmovin writes output to S3 or another cloud storage. ChangeThisFile returns the file directly in the HTTP response. Remove the S3 download step and write response.content to disk.
5. Update environment variables: Replace BITMOVIN_API_KEY with CTF_API_KEY.

Rollback plan

Bitmovin plans are typically monthly or annual. Keep your account active during migration:

1. For the first two weeks, run parallel conversions and compare output files. Check resolution, codec, file size, and playback compatibility in your target players.
2. ChangeThisFile uses FFmpeg with default settings for the target format. Default H.264 MP4 and VP9 WebM settings are broadly compatible with all major browsers and devices. If you need specific bitrate, resolution, or codec parameters, those aren't configurable in ChangeThisFile — stay on Bitmovin for those requirements.
3. If your application plays videos in a web player, test playback after migration. FFmpeg-encoded files are compatible with HTML5 video across all modern browsers.
4. Cancel Bitmovin subscription after 30 days of confirmed production operation.

Common migration questions

Will video quality be as good?
ChangeThisFile uses FFmpeg with default settings. Bitmovin uses optimized encoding pipelines that can be configured for specific quality/bitrate targets. For simple format conversion without quality tuning, FFmpeg defaults are broadly acceptable. For production video delivery where quality is a competitive differentiator, Bitmovin's encoder is better.

Does ChangeThisFile support H.265/HEVC output?
ChangeThisFile supports MP4, WebM, MKV, AVI, MOV, and other container formats. The codec used within each container is handled by FFmpeg defaults. H.265 is not available as a configurable option.

What's the file size limit for video conversion?
ChangeThisFile's free tier has a 25MB upload limit. Paid plans support larger files. Large video files (HD and 4K) typically exceed 25MB — ensure your CTF plan's limit matches your video file sizes before migrating.

Can ChangeThisFile extract audio from video?
Yes — MP4→MP3, MP4→WAV, MP4→AAC, MKV→MP3, and other video-to-audio extractions are supported. This is one area where ChangeThisFile is fully comparable to Bitmovin's audio extraction capabilities.

Does ChangeThisFile support GIF generation from video?
Yes — MP4→GIF is supported. Useful for thumbnails and preview animations.

Bitmovin is overbuilt for simple format conversion. If your use case fits ChangeThisFile's model — upload file, receive converted file — the migration removes a large amount of SDK and pipeline code and eliminates encoding-minute billing. Get a free API key and test your most common video conversion before deciding.