Novus Convert
Convert files
Working landing-page directory

Every live conversion, in one directory

Browse every published input-to-output route backed by a real browser-side engine. Desktop and mobile navigation point to this same capability source.

Image conversions

547 working routes

Video conversions

628 working routes

Audio conversions

180 working routes

Document conversions

439 working routes
JSONJSON data42 verified outputs
JSON to CSVJSON to TSVJSON to YAMLJSON to YMLJSON to XMLJSON to TXTJSON to XLSXJSON to ODSJSON to NPYJSON to ENVJSON to FDFJSON to XFDFJSON to BIBJSON to RISJSON to GRAPHMLJSON to GEXFJSON to DOTJSON to JSONLJSON to NDJSONJSON to TOMLJSON to INIJSON to ICSJSON to VCFJSON to OPMLJSON to M3UJSON to M3U8JSON to MSGPACKJSON to CBORJSON to BSONJSON to ARROWJSON to FEATHERJSON to SQLITEJSON to POJSON to POTJSON to XLFJSON to XLIFFJSON to STRINGSJSON to ARBJSON to RESXJSON to ANDROIDXMLJSON to I18NEXTJSON to QTS

Data conversions

240 working routes
PBProtocol Buffers message1 verified outputs
PB to JSON

Archive conversions

93 working routes

Ebook conversions

47 working routes

Vector & CAD conversions

207 working routes

Font conversions

19 working routes
TTCTrueType Collection1 verified outputs
TTC to ZIP

About the conversion directory

This is the complete, working directory of everything Novus Convert can convert — 2400 input-to-output routes, each one backed by a real browser-side engine rather than a placeholder. Every route listed here has a dedicated page with a live converter, so you can go from "does this work?" to a finished download without leaving the browser.

The directory is generated from the same truthful capability manifest that powers the converter's own output menus. If a route appears here, it has an implemented engine and validates its output before enabling a download; routes that cannot yet be produced and verified simply are not listed. Desktop and mobile navigation both point at this single source, so what you see is exactly what runs on your device today.

Because processing is local, batch conversion is the natural way to work: add a mixed set of files, give each its own output, and download the successful results one by one. Nothing is uploaded, so there is no queue, no watermark, and no size-based paywall.

Conversion directory questions, answered

How many conversions are available right now?

There are 2400 published conversion routes, and the number grows as new engines ship. Each is a real, validated conversion — not a redirect to an upload service — and each has its own landing page with a working converter and format background.

Is every listed conversion actually working?

Yes. The directory is derived from the live capability manifest, and a build-time check refuses to publish a route that has no implemented, output-validating engine. That is a deliberate design choice: you should never encounter a listed conversion that quietly fails.

Do these conversions run on a server?

No. All published conversions run locally in your browser with WebAssembly engines (FFmpeg for media, LibRaw for camera RAW, pdf.js and pdf-lib for documents, SheetJS for spreadsheets, libarchive for archives, and more). Your files never leave your device.

Can I convert several files at once?

Yes. Open any route or the general batch converter, add multiple files, and choose an output per file. Since there is no upload step, batches are limited only by your device's memory, and you download each validated result independently.

What if the conversion I need isn't listed?

If a route is not in the directory, this release cannot yet produce and validate it in the browser. Check the format directory for a reference guide, or send a request with the exact input and output you need so it can be prioritized.