API roadmap

Conversion API roadmap

These are planned automation endpoints from competitor research. The current site is browser-first and does not sell API keys today, but this roadmap helps users and search engines understand what FreeConverter.net should build next.

No API keys today Browser tools live Server API planned Privacy rules required

Planned endpoints

Use our API conversion roadmap

Live tools link to the current browser version. Planned entries need a real API backend, job queue, file deletion policy, and documented limits before launch.

audio converter api Browser tool live, API planned video converter api API engine planned doc converter api Related tool live, API planned image to text api Browser tool live, API planned webm to mp4 api Video engine planned doc to jpg api Document renderer planned doc to png api Document renderer planned docx to png api Document renderer planned mp3 converter api Browser tool live, API planned html to word api Related tool live, API planned photo to text api Browser tool live, API planned svg to png api Browser tool live, API planned video to gif api Video engine planned html to pdf api Related tool live, API planned word to pdf api Document renderer planned pdf to text api Browser tool live, API planned pdf to csv api Extraction engine planned pdf to html api Extraction engine planned pdf to xls api Extraction engine planned web to pdf api Browser/server renderer planned

Build order

Best API features to build first

The first API should focus on tools already proven in the browser. That keeps the product honest and lowers technical risk.

OCR and photo to text API

Image to text has clear demand from students, office users, and automation workflows.

PDF to text API

Text extraction is lighter than full document conversion and useful for search, records, and data entry.

Image conversion API

SVG to PNG, WebP to JPG, JPG to PNG, and PNG to JPG are strong fit for automated image pipelines.

Audio conversion API

MP3, WAV, and M4A conversion can serve creators, transcription tools, and podcast workflows.

Example design

What a future API request could look like

This is a planning example only. It is not a live endpoint yet.

Job request

POST /api/v1/jobs
Content-Type: multipart/form-data

source_format=pdf
target_format=text
file=@document.pdf
callback_url=https://example.com/done

Job response

{
  "job_id": "job_123",
  "status": "queued",
  "delete_after_minutes": 60
}

Current live tools

Use these tools while API access is planned

OCR

Image to Text OCR

Extract text from images in your browser.

PDF

PDF to Text

Extract selectable PDF text locally.

IMG

Image Format Converter

Convert browser-supported images to JPG, PNG, or WebP.

MP3

Audio to MP3

Convert supported audio files to MP3 locally where possible.

API FAQ

Conversion API FAQ

Can I get an API key today?

No. This is a roadmap page. FreeConverter.net does not currently provide API keys, billing, or automated server jobs.

Why publish API pages before the API is ready?

It helps record real user demand and gives a clear public build order without misleading users into paying for something that does not exist yet.

What must be added before launch?

A production API needs authentication, rate limits, upload limits, status endpoints, logs, retention rules, abuse protection, and a deletion policy.

Will files be stored?

Future API file handling must be documented clearly. The safest first policy is temporary processing with automatic deletion after a short retention window.