Each credit equals one second of processing time (rounded up), based on actual processing time — not video length. Typical usage in production (90-day median): trim ~3 credits/job, convert ~7 credits/job (larger files scale up), compose ~5 credits/job, overlay ~15 credits/min (estimate).
Yes. Browser tools work without signup, but anonymous usage is limited to 5 jobs per 24 hours. Create an account for API access and additional credits.
Browser tools accept MP4, WebM, MOV, and AVI inputs. Convert outputs MP4, WebM, or GIF. Compose supports MP3 audio and SRT/VTT subtitles. For API validation, use the /video/validate endpoint in the docs.
Video jobs are queued and return a job ID. Poll the job status endpoint to retrieve the output when it completes.
Yes. You can configure webhooks per API key to receive job completion callbacks. If you prefer, you can also poll job status; browser tools can send email notifications when a job finishes.
The API returns an "insufficient credits" error (HTTP 402) and the job will not start until you add more credits or upgrade.
Anonymous tools use a server-side proxy so API keys stay private. Access to rate-limit data is restricted to service roles. For retention details, see the privacy policy.
Processing times depend on the video size and operation complexity. Most operations complete within seconds to a few minutes.
