Help center

How can we help?

Direct answers to the questions that matter before you upload a file or build an integration. Product limits are also listed on the pricing page.

Getting started with your first conversion

For a quick image conversion, choose a live pair under Converters and upload a file. Anonymous image conversion is limited to 15 MB. Sign in for the dashboard uploader, saved history, larger plan limits, and queue-backed document, spreadsheet, audio, video, and archive jobs.

Understanding retention and automatic deletion

Retention starts after a job completes. Available choices are delete-immediately, 1 hour, 24 hours, and 7 days, depending on plan. Delete-immediately includes a five-minute grace period so the result can be downloaded. Expiration hard-deletes objects from storage; download URLs are short-lived and signed.

Using the dashboard uploader and history

The uploader sends the file directly to object storage with a presigned URL, then creates a conversion job. History shows queued, processing, finalizing, completed, failed, cancelled, and expired states. A completed job receives a fresh download link when requested; an expired job no longer exposes one.

Creating API keys and calling the REST API

API keys are available on Business and Enterprise. The synchronous endpoint is intended for bounded in-process engines; use POST /api/v1/uploads followed by POST /api/v1/jobs for heavy work. Keys are shown once, stored as hashes, and support convert:write, convert:read, and jobs:read scopes.

Registering webhooks

Create webhook endpoints in the dashboard and subscribe to conversion.completed, conversion.failed, or conversion.expired. Convyx signs the raw JSON body with the endpoint secret and sends a stable delivery ID. Async worker jobs emit webhooks; synchronous API conversion does not.

Troubleshooting a failed conversion

First confirm the source extension matches the actual file and that the target pair is marked Live. Corrupt input, encrypted documents, unsupported codecs, engine size limits, and storage upload mismatches can all fail safely. Failed accepted jobs consume quota because processing resources have already been reserved.