Can AI replace FileChanger?
The conversion is other people's software. Pandoc, ImageMagick and FFmpeg do the actual work, the format list looks enormous because those three projects are enormous, and a coding agent can wire all of them behind an upload form and a REST endpoint in one sitting. What a subscription buys is not the conversion, it is somebody else running a box that eats untrusted files from strangers all day without falling over, and keeping a few hundred format pairs working after every upstream release. Point it at your own files on your own machine and most of that risk simply is not yours, which is why this one is a yes.
01What it costs
Checked Aug 13, 2026 · source: filechanger.io. The free tier is real and permanent: 200 MB each of documents, images and audio per month, 50 MB of video, and API keys plus MCP access included.
| Plan | Monthly | Billed yearly | What you get |
|---|---|---|---|
| Free | Free | Free | 200 MB documents + 200 MB images + 200 MB audio + 50 MB video per calendar month; about 200 document conversions; API keys and MCP access |
| Starter | $39 | — | Per month: 100 GB documents, 100 GB images, 50 GB audio, 10 GB video; about 100,000 document conversions; API + MCP |
| Pro | $99 | — | Per month: 350 GB documents, 350 GB images, 200 GB audio, 50 GB video; about 350,000 document conversions; API + MCP |
Hidden costs: Allowances are separate by format group and meter input bytes, not output size; no annual plan is published
02Could AI build it for you?
The core job: Accept a file, shell out to pandoc, ImageMagick or FFmpeg depending on what it is, and hand the converted bytes back over HTTP or MCP.
What a working version needs:
- pandoc
- FFmpeg
- ImageMagick
- LibreOffice headless for Office formats
- Typst or a LaTeX install if you want PDF out
Submitted by the person who runs FileChanger, so the verdict is deliberately the unflattering one: the engines are all open source and the DIY build is a sitting. Pricing checked 2026-08-07.
03What you'd give up
- sandboxing, because your version runs files straight through the same toolchain as everything else on the machine
- the long tail of format pairs, where the fix is usually a missing font, a filter flag or an upstream bug
- queueing and timeouts for large video, which is where the compute bill actually lives
- a hosted MCP server and API keys your other tools can reach from anywhere, not just from localhost
- somebody else being on call when a LibreOffice or LaTeX upgrade quietly breaks PDF output
Nobody pays for the conversions that work. They pay for the awkward ones: the DOCX with tracked changes, the HEIC nobody can open, the MXF from a camera, the 4 GB video that has to finish while a browser tab is still open. Doing those reliably means keeping a toolchain installed, patched and fenced off from the files it is fed, and doing it for other people means doing it while strangers upload whatever they like. That upkeep is the product. The convert button is a weekend.
04Free and cheaper alternatives
A self-hosted web converter that wraps the same engines, with accounts and a job list already built. One container and you own the whole pipeline.
Versus paying: It provides a self-hosted web interface rather than FileChanger's managed one-call API, so uptime, scaling, security and integration glue are yours.
github.com →Converts images and documents in the browser tab itself, so the file never leaves the machine. Video is the exception and needs their server or yours.
Versus paying: It has no equivalent unified managed conversion API, supports a narrower set of jobs, and private video conversion needs a separate daemon.
vert.sh →If the job is only documents, the paid service is a web form on top of this. Installer, twenty years of releases, and no upload step.
Versus paying: It only handles document formats from the command line, with no image, audio or video conversion and no hosted API.
pandoc.org →05The build prompt
Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.
Build me a personal file conversion service in an empty repo. Requirements:
- Python 3.12, FastAPI, uv for dependencies, SQLite for job state. One process,
no broker, no microservices, no alternative stacks.
- Never write a converter. Shell out to pandoc for markup and documents,
LibreOffice headless for Office, ImageMagick for images, FFmpeg for media.
- POST /convert takes a file, a source and a target format and returns the bytes
below a size threshold set in config. Above it the same route returns a job
id, GET /jobs/{id} reports its state and GET /jobs/{id}/result streams the
file. One background worker thread is enough, do not add Celery.
- Build the format matrix at startup from `pandoc --list-input-formats`,
`--list-output-formats`, `ffmpeg -formats` and `magick -list format` rather
than hardcoding it, and serve it at GET /formats.
- Treat every upload as hostile: convert in a temp dir with a wall-clock
timeout, an output size cap and no network, then delete the inputs whether it
worked or not. Log the failing command and its stderr, never return either.
- Ship an MCP server over stdio using the official Python SDK, exposing convert
and formats as tools so agents can convert without going through HTTP.
- Authenticate with API keys stored hashed in SQLite. Show the plaintext once at
creation and support revocation.
- One HTML page, no JS framework: pick a file, pick a target from /formats,
download the result.
- One Dockerfile installing pandoc, typst, libreoffice-core, imagemagick and
ffmpeg, a compose file with a volume for the database, config in .env and a
committed .env.example.
- Out of scope: accounts, billing, metering, quotas, telemetry, multi-tenancy
and any hosted control plane.
- Test one round trip per engine (Markdown to PDF, PNG to WebP, WAV to MP3), an
oversized upload and a conversion that hits the timeout. README covers setup,
formats, security assumptions and where data lives. Finish by running the
tests and listing the commands used.06Open-source starting points
- Pandoc: The document half of any converter: markup, Office, EPUB and PDF in essentially any direction.
- FFmpeg: The audio and video half. Everything that converts media is calling this underneath.
- ImageMagick: Images, including the formats browsers refuse to open.
App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.
Get new verdicts in your inbox.
One short email when new verdicts land: what AI can now do for you, and what it still gets wrong. No spam. Unsubscribe anytime.