Skip to main content
Quickstart
Convertly is a media platform for products that ingest, process, deliver, and automate files. Most teams start in one of four places: a direct API call, edge delivery through the Image CDN, the hosted dashboard, or a background job with webhooks.
API keys are shown once when created. Store yours in a server environment variable, never in client-side browser code.

Platform at a glance

Video streaming (adaptive HLS/DASH playback) lives under Streams in the dashboard. See Video streaming.

Create an API key

Open API keys in the dashboard

Sign in to convertly.sh/app, open your account menu (top right), choose Settings, then scroll to API keys.Workspace owners and admins can create and revoke keys. Other members can use existing keys.

Store the key on your server

Send it on every API request:
x-api-key is also supported. See Authentication.
Image CDN signing keys are separate from API keys. Manage delivery namespaces and signing keys under Image CDN → Delivery in the dashboard.

Choose your first path

Convert a file (API)

Best when you need a processed file back immediately in your backend.

Deliver through Image CDN

Best when images or video already live on your site or in storage and you want transform URLs.

Use the dashboard

Best for manual batches, Forma AI, and testing transforms before you wire an integration.

Queue background work

Best for large batches that should finish after the upload request returns.

Convert a file with the API

Send multipart/form-data to POST /api/convert. Convertly validates your plan limits, processes the file, and returns metadata plus a downloadUrl.
The response includes a files array. Each item has the output filename, MIME type, size savings, and downloadUrl.

Media conversion reference

Supported formats, resize modes, archives, and production patterns.

Deliver with the Image CDN

The Image CDN transforms images and video at request time. responsive sizes, format negotiation (format=auto), poster frames, trimmed clips, and smart cropping. You do not pre-generate variant files.

Pick a delivery namespace

Open Image CDN → Delivery and copy your default namespace, or create one for each site or product surface.

Connect a source

Choose where Convertly fetches originals from:
  • Origin source. a deployed public HTTPS site, bucket, or CDN folder (Sources)
  • Convertly Storage. upload files in Assets and use the file UUID or CDN slug in URLs

Preview transforms

Use Image CDN → Transform Lab to preview posters, clips, and image transforms and copy a production-ready URL before you ship it.

Install the SDK (optional)

Drop in <ConvertlyImage> or a framework loader so your app builds CDN URLs automatically.
Installing @convertly-sh/image only rewrites URLs. You still need an origin source or stored file before CDN URLs resolve. The SDK does not upload your repo or sync local folders.

End-to-end CDN setup guide

Origin vs storage, framework wiring, and verification checklist.

Use the dashboard without code

You can run most of the platform from convertly.sh/app before writing integration code:

Dashboard workflows

Build repeatable pipelines without deploying your own workers.

Queue a background job

Use POST /api/jobs when files should upload once, process on Convertly workers, and be polled later.
Poll status:
Add webhooks when your app should react as soon as a job or workflow finishes.

API endpoint map

Next steps

Dashboard workflows

Use the hosted app for files, Image CDN tabs, Forma AI, and repeatable workflows.

Authentication & limits

Headers, WordPress site tokens, and plan quotas.

Plan limits

Full quota tables for every plan tier.

SDKs

@convertly-sh/sdk, @convertly-sh/image, and PHP client.

API reference

Interactive schemas and playground examples.

Use cases

SaaS uploads, marketplaces, ecommerce, and agency batches.

MCP for AI agents

Let Cursor, Claude, and Codex work with approved local folders.

Image CDN setup

Wire origins, namespaces, and the SDK on your site.
Last modified on July 28, 2026