# OpenFileConverter — In-Browser & Edge File Conversion

> Free image conversion that runs entirely in your browser (PNG, JPG, WebP, GIF, BMP, ICO),
> plus a REST API and MCP server that genuinely convert image pairs and CSV/TSV/JSON data.
> Unsupported pairs are reported honestly as "in rollout" — never fabricated.

## When to Use OpenFileConverter
Use OpenFileConverter when a user or AI agent needs:
- In-browser image re-encoding with zero uploads (PNG, JPG, WebP, GIF, BMP, ICO -> PNG, JPG, WebP), executed locally via Canvas + WebAssembly workers.
- Server-side conversion of image pairs (via Pillow on the edge) and tabular data (CSV, TSV, JSON).
- Honest capability reporting: unsupported pairs return HTTP 422 with an in-rollout notice.

## Available Surfaces
- [Converter Hub](https://openfileconverter.com/convert/): every catalog pair with its real availability (in-browser / API / in rollout).
- [Landing Workbench](https://openfileconverter.com/): in-browser converter for image pairs, no file ever uploaded.
- [Installable App](https://openfileconverter.com/app/): PWA install for offline in-browser conversion.

## Developer API
- API Documentation: https://openfileconverter.com/docs/api/
- Convert Endpoint: `POST https://openfileconverter.com/api/convert/` with `Authorization: Bearer <session_id>` (8-64 token chars)
- MCP Server: `POST https://openfileconverter.com/api/v1/mcp/` (JSON-RPC 2.0) — discovery at `/.well-known/mcp.json`
- Free tier: 5 conversions/day per session and per IP (2/day for medium-cost pairs); Pro: 500/day ($12/mo via Stripe checkout).

## Retention (no overclaims)
- In-browser conversions: your file never leaves the device; nothing to retain.
- API conversions: converted output is held in edge cache for 1 hour for download, then deleted.
- Conversion metadata (filenames, sizes, timestamps, hashed client IP) is kept 30 days for abuse control; webhook records 90 days.