File Conversion API
Convert images, videos, audio and documents with your own self-hosted conversion API.
One service for your file conversion workflows
50 endpoints · Image, PDF, video and document tools · Your own server
API Documentation
The self-hosted API uses the same conversion engines as the server tools. Requests return the converted file directly. There is no public hosted API yet.
Authentication
Create a personal API key in Dashboard → API keys and send it as a Bearer token. Personal keys expire after 90 days and can be revoked at any time. The server owner can also configure CONVERSION_API_KEY. Never put either kind of key in public frontend code.
Request
POST /api/v1/convert/mp4-to-mp3
Authorization: Bearer YOUR_API_KEY
Content-Type: multipart/form-data
files: your input file
settings: {"output":"mp3","bitrate":"128"}Limits and response
Two simultaneous conversions, 1 GB total input, 100 MB output, and a two-minute processing timeout. Video/audio outputs are limited to ten minutes. Success returns a downloadable file. Errors return JSON with an error field and an HTTP error status.
API Job Builder
curl --fail-with-body \
-H "Authorization: Bearer $FRESHCONVERT_API_KEY" \
-F 'files=@input.mp4' \
-F 'settings={"output":"mp3"}' \
http://127.0.0.1:4321/api/v1/convert/mp4-to-mp3 \
--output result.mp3Set FRESHCONVERT_API_KEY in your terminal to the server’s configured key. Replace the input path. No credentials are stored in this page.
Available endpoints
/api/v1/convert/video-converter/api/v1/convert/audio-converter/api/v1/convert/mp3-converter/api/v1/convert/mp4-to-mp3/api/v1/convert/video-to-mp3/api/v1/convert/mp4-converter/api/v1/convert/mov-to-mp4/api/v1/convert/mp3-to-ogg/api/v1/convert/video-to-gif/api/v1/convert/mp4-to-gif/api/v1/convert/webm-to-gif/api/v1/convert/mov-to-gif/api/v1/convert/avi-to-gif/api/v1/convert/apng-to-gif/api/v1/convert/gif-to-mp4/api/v1/convert/gif-to-apng/api/v1/convert/image-to-gif/api/v1/convert/gif-maker/api/v1/convert/video-compressor/api/v1/convert/mp3-compressor/api/v1/convert/wav-compressor/api/v1/convert/gif-compressor/api/v1/convert/crop-video/api/v1/convert/trim-video/api/v1/convert/docx-to-pdf/api/v1/convert/word-to-pdf/api/v1/convert/document-converter/api/v1/convert/pdf-to-word/api/v1/convert/pdf-to-epub/api/v1/convert/epub-to-pdf/api/v1/convert/epub-to-mobi/api/v1/convert/ebook-converter/api/v1/convert/pdf-compressor/api/v1/convert/flatten-pdf/api/v1/convert/resize-pdf/api/v1/convert/unlock-pdf/api/v1/convert/protect-pdf/api/v1/convert/crop-pdf/api/v1/convert/extract-images-from-pdf/api/v1/convert/png-to-svg/api/v1/convert/archive-converter/api/v1/convert/rar-to-zip/api/v1/convert/image-converter/api/v1/convert/jpg-to-pdf/api/v1/convert/heic-to-jpg/api/v1/convert/webp-to-png/api/v1/convert/webp-to-jpg/api/v1/convert/image-compressor/api/v1/convert/pdf-to-jpg/api/v1/convert/html-to-pdfImage and HTML API limits
Image APIs accept one still image up to 24 megapixels. Optional width, height, quality (1–100) and background settings control the result. PDF-to-JPG returns a ZIP with up to 50 pages at 72 DPI. HTML-to-PDF accepts a self-contained HTML file, disables scripts and blocks every network request; embed required image resources as data URLs.
Website screenshots
Remote website screenshots are not enabled. An arbitrary-URL fetch service needs a separately isolated network worker, DNS pinning and SSRF validation before public exposure. Cloud storage imports and social OAuth also require owner-controlled provider configuration.