CloudConvert has been a developer favorite since 2012. It's polished, well-documented, and handles obscure formats well. ChangeThisFile takes a different bet: a hybrid architecture where common conversions run entirely in the browser (zero upload, zero server cost) and a clean API covers everything else with a genuinely free tier.

This comparison covers pricing, format coverage, privacy, API experience, and the specific scenarios where each tool wins.

Quick verdict

For individuals and small teams: ChangeThisFile. Free browser tool with no signup, plus 1,000 free API calls/month makes it cost-zero for most use cases.

For developers with high conversion volume: Both are viable depending on format needs. CloudConvert's per-minute billing model can get expensive fast; ChangeThisFile's $29/mo Hobby tier covers 10,000 conversions flat.

For privacy-sensitive workflows: ChangeThisFile wins on many common formats — JPG, PNG, WebP, HEIC, CSV, JSON, YAML, fonts, and more convert entirely client-side, files never reach any server.

For exotic format support: CloudConvert. Their 200+ format catalog is broader, particularly for legacy and professional formats.

Pricing comparison

PlanChangeThisFileCloudConvert
Free tier1,000 conversions/month (no card)None — pay-as-you-go only
Entry paid$29/mo — 10,000 conversions~$0.0048/conversion-minute (varies)
$100/mo equiv.$99 Startup — 50,000 conversions~20,800 conversion-minutes
High volume$499 Scale / $1,999 GrowthVolume packages available
Browser toolFree, no signup, no limit25 free conversions/day (web UI)

CloudConvert bills by conversion minutes — the wall-clock time your job takes to run on their servers. A 10-second video transcode and a 10-second document conversion are priced the same per minute, but video is far faster per-unit than documents. Heavy document workflows cost more than you'd expect.

ChangeThisFile bills per conversion (each API call = one conversion), which is more predictable. Short jobs and long jobs cost the same.

Feature comparison

FeatureChangeThisFileCloudConvert
Free API tierYes — 1,000/mo, no cardNo
Browser tool (no signup)YesYes (25/day limit)
Client-side conversionsYes — 161 routes run in browserNo — all server-side
Conversion routes634200+ formats, many route pairs
API authenticationBearer tokenBearer token
WebhooksNoYes
Job queuing / asyncNo (sync API)Yes (async job system)
S3/storage importNoYes
Conversion settingsBasic (target format)Advanced (quality, fps, codec, etc.)
Self-hosted optionNoNo

Format and route coverage

CloudConvert lists 200+ supported formats on their site. Their catalog is genuinely broad, covering CAD formats (DWG, DXF), specialized image formats (EXR, HDR), and professional video codecs. If you work with unusual or industry-specific formats, CloudConvert has a strong advantage.

ChangeThisFile covers 634 specific source→target route pairs across 82 format definitions. The focus is on high-traffic conversions: image (JPG, PNG, WebP, HEIC, SVG, AVIF, GIF, BMP, ICO), documents (PDF, DOCX, ODT, RTF, HTML), spreadsheets (XLSX, CSV, JSON, TSV), video (MP4, MKV, WebM, AVI, MOV, GIF), audio (MP3, WAV, FLAC, AAC, M4A), ebooks (EPUB, MOBI, AZW3), archives (ZIP, RAR, 7Z, TAR), and fonts (TTF, OTF, WOFF, WOFF2).

For most web-facing and developer use cases, the coverage overlap is high. The gap shows up in niche professional formats.

Privacy and data handling

This is where the architectures diverge most sharply.

ChangeThisFile client-side routes (161 routes covering all major image formats, CSV/JSON/YAML/TSV/XML/TOML, DOCX→HTML, HTML↔Markdown, JPG/PNG→PDF, HEIC, PSD, XLSX, fonts): files are processed entirely in your browser using JavaScript. Nothing is uploaded. No server sees your data. This is enforced by architecture, not just policy.

ChangeThisFile server-side routes (video, audio, complex documents, archives): files are uploaded over HTTPS, converted, returned, and automatically deleted. There is no retention.

CloudConvert is entirely server-side. All files upload to their infrastructure. They have a privacy policy and do not claim to retain files beyond a short period, but every file does traverse their servers regardless of format.

For sensitive documents, financial data, or private images, client-side conversion offers a structural privacy guarantee that server-side tools cannot match regardless of their policy.

API and developer experience

ChangeThisFile API is intentionally simple: one endpoint (POST /v1/convert), multipart file upload, Bearer token auth, synchronous response. Get your API key at changethisfile.com/v1/keys/free (no card).

curl -X POST https://changethisfile.com/v1/convert \
  -H "Authorization: Bearer ctf_sk_your_key" \
  -F "file=@input.docx" \
  -F "source=docx" \
  -F "target=pdf" \
  --output result.pdf

CloudConvert API is more powerful and more complex. It uses an async job system: create a task, poll for completion, download the result. Supports webhooks, S3 import/export, and detailed per-format settings (video bitrate, image quality, page ranges, etc.).

For simple integrations (upload file → get converted file back), ChangeThisFile's synchronous API is less code. For complex pipelines (batch jobs, webhooks, storage integration), CloudConvert's architecture is better suited.

When to choose which

Use caseRecommended
Individual file conversion, no signupChangeThisFile (browser tool)
Privacy-sensitive files (images, documents, data)ChangeThisFile (client-side routes)
Free API tier for hobby/side projectsChangeThisFile
Simple REST API integrationChangeThisFile
Niche or professional format support (CAD, EXR, etc.)CloudConvert
Advanced conversion settings (bitrate, DPI, codec)CloudConvert
Async job queuing with webhooksCloudConvert
S3/cloud storage integrationCloudConvert

If you're evaluating CloudConvert because you need a quick conversion API and don't want to pay before you know it works — ChangeThisFile's free tier is a better starting point. 1,000 conversions/month with no card covers most side projects entirely. For high-volume pipelines or niche format needs, CloudConvert's job system and format breadth are worth the cost.