API changes

Every change to what you can send and what comes back, newest first. The version of the OpenAPI specification is the newest entry here: 1.10.2.

1.10.2 · 22 November 2026, 19:12 UTC

A renderer that has no room when it is offered a job returns it to the queue unstarted: started_at goes back to null and the job waits for another slot up to its max_wait_seconds, then ends expired with failure_code no_capacity if none takes it. Such a job used to end failed with failure_code no_capacity after three refusals. failed with no_capacity stays documented as given back unstarted, not charged: send the same job again.

1.10.1 · 22 November 2026, 18:55 UTC

A job can end failed with failure_code no_capacity: a renderer took it and gave it back before rendering because it no longer had room. Nothing was rendered or charged; send the same job again. Job 72a4e403 ended this way on 22 November. Stated: a job sent while every slot is busy waits in the queue for the next free slot and is not refused, and free_slots 0 from the capacity route means a new job will wait. Send a job once with max_wait_seconds as long as you will wait (up to 86400, for example 7200) rather than resending it each time it expires after the default 900 seconds.

1.10.0 · 22 November 2026, 03:50 UTC

ffmpeg.timeline_export.v1: a source whose frame starts wander around a steady rate, as a phone or a browser recording does, is first put on that rate’s grid, for clips and video picture segments at every speed. A 30 fps recording on a 30 fps canvas used to show some frames twice and lose others; it now shows each once. Sources on a regular grid are untouched, and so is a source with no steady rate. The definition is published as code: /reference/frame-conform.mjs. The millisecond of the frame rule is a millisecond on any time base; on a file that counts time in 600ths of a second it used to act as 1.67 milliseconds.

1.9.2 · 22 November 2026, 02:57 UTC

remotion.render.v1: a render in a MOV carries exact frame times, as an MP4 render already did. A 30 fps MOV used to read 29.998 fps with frame times rounded to the millisecond. The picture and sound are the same bytes. Stated: in_seconds and source_in_seconds of a timeline export count from the file’s start, the earliest start of its picture or sound. In a file whose picture begins after its sound the picture runs up to one output frame behind the sound, and the first frame is shown until the picture begins.

1.9.1 · 22 November 2026, 02:47 UTC

ffmpeg.timeline_export.v1: a source frame that begins up to one millisecond after an output frame’s instant counts as on display at it, for clips and video picture segments at every speed. A file whose frame times are rounded to the millisecond, such as a Remotion render or a WebM file, used to lose every third frame at 30 fps and show others twice.

1.9.0 · 22 November 2026, 02:30 UTC

Accounts, sign-in and server API keys are kept by PennyCompute. A server API key made before this release that was in use when it went out kept working and is listed under Server API keys as Made before 22 November 2026. Any other is no longer accepted: make a new one under Server API keys in the dashboard. Someone who signed up before this release chooses a new password with Reset password. People: an owner or admin invites people to the organization by email with a role (owner, admin, developer or billing), changes roles and removes people, in the dashboard or with GET /v1/org/members, POST and DELETE /v1/org/members/{id}, POST /v1/org/invitations and DELETE /v1/org/invitations/{id}. Only an owner acts on another owner, and an organization keeps at least one owner (409 last_owner). A dashboard call the person's role does not allow answers 403 missing_role; adding funds used to answer billing_role_required. GET /v1/auth/me names who is calling: for a key its id and scopes, for a signed-in person member with their role. key_mode is gone, and a key has no mode: creating one takes a name and scopes.

1.8.0 · 22 November 2026, 00:04 UTC

POST /v1/assets hosts a complete Remotion bundle: send up to 256 nonempty relative files with their byte lengths and SHA-256 values, PUT every returned upload, and pass the returned serve_url to remotion.render.v1. A file can be up to 100 MB and a bundle up to 1 GB. Relative JavaScript chunks and other bundle files are served from the same folder for 24 hours. Hosted Remotion bundles are served only from the isolated quiet-field-7f3c.buildngrowsv.workers.dev origin. That origin has no buyer API, account session or cookies, and api.pennycompute.com refuses bundle reads. Bundle preparation returns bundle_origin_unavailable without writing a manifest if that origin is missing or invalid. Uploaded files carry X-Content-Type-Options: nosniff. Bundle content types are inferred from their paths and bundle HTML carries a Remotion-compatible Content-Security-Policy. Single-file uploads accept only documented media types, and every input link is sandboxed with a default-src none Content-Security-Policy. The existing scheduled handler sweeps expired inputs, bundle files and bundle manifests from the media bucket after a 48-hour deletion margin. It restarts a rejected R2 cursor and rechecks an object before deletion so a concurrent renewal is kept. The JavaScript client adds uploadBundle(files), and the Remotion guide has an end-to-end example from the build folder to a submitted job.

1.7.4 · 22 November 2026, 00:39 UTC

ffmpeg.timeline_export.v1: a video picture segment follows the frame rule a clip follows, at any speed: output frame n shows the source frame on display at source_in_seconds plus n times playback_rate divided by the frame rate. A segment whose in-point falls between two source frames used to start one frame later. Stated: input with no colour matrix tag is taken as BT.709 and its samples are not converted; a full-range input is brought to limited range; input tagged with another matrix or coded as RGB is converted.

1.7.3 · 21 November 2026, 21:59 UTC

ffmpeg.timeline_export.v1: which source frame each output frame of a clip shows is now a stated rule, the frame on display at that instant. A clip whose in-point falls between two source frames starts on the earlier one; it used to start on the later one, shown twice. A plain clip on a canvas of another frame rate repeats or drops different frames than before. The rule is on the timeline guide.

1.7.2 · 21 November 2026, 21:41 UTC

Captions: renderers have DejaVu Sans in regular and bold, for ffmpeg.timeline_export.v1 and ffmpeg.caption_burn.v1. A caption that names DejaVu Sans used to be drawn in Helvetica.

1.7.1 · 21 November 2026, 21:30 UTC

A job that is rendering while the service is updated keeps rendering and is handed in when done. It used to start again on another renderer, or fail with lease_expired. A submit or a read in those few seconds can still answer 502 or 503. A job ends slightly sooner: the finished file is measured while its size is looked up.

1.7.0 · 21 November 2026, 20:55 UTC

ffmpeg.timeline_export.v1: canvas takes crf, 0 to 51, and preset, a libx264 preset, for every picture encode in the job. Left out, both follow the resolution as before. Stated: a webhook delivery arrives about 1.1 seconds after the job’s completed_at, as measured.

1.6.3 · 21 November 2026, 20:53 UTC

A webhook delivery is sent as soon as the job has ended; it used to follow by up to 3 seconds. When it arrives the job read already shows the final state, the charge and the output link. The first request after a quiet spell takes about 5 seconds; it used to take 9 to 10. A Remotion render whose browser does not start on one renderer is tried on another before the job can read runner_failed. The job reference carries the measured time of a short 1080p export.

1.6.2 · 21 November 2026, 20:45 UTC

Corrected: registering a webhook endpoint answers with the endpoint alone: id, name, url, events, status, created_at and updated_at. The pages named a further value that the answer does not carry.

1.6.1 · 21 November 2026, 20:22 UTC

Jobs are faster: a job goes to the fastest renderer with a free slot, and a finished job reads succeeded without waiting behind its progress reports. Measured times for a short timeline export and a short Remotion render are on the job reference page. POST /v1/jobs answers once the job exists, in about a second; it used to wait until the job had been offered to renderers. The first request after about a minute with none takes 9 to 10 seconds. Corrected: GET /v1/services/{service_id}/capacity could report free_slots 0 after a quiet spell while renderers were ready.

1.6.0 · 21 November 2026, 19:42 UTC

A new account starts with $5 in its prepaid balance. GET /v1/billing/balance returns prepaid_micros 5000000 before the first top-up. GET /v1/invoices returns one statement for each calendar month (UTC) with charges, with the id st_ and the month. The current month is a draft and a past month is issued. GET /healthz reports settlement: whether charges for finished work reach the balance within a few minutes. Stated: only a dashboard member with the owner, admin or billing role can add funds. Others get 403 billing_role_required.

1.5.4 · 21 November 2026, 18:55 UTC

Stated: a timeline export is encoded with libx264, at preset fast for proxy_480p and 720p and veryfast for 1080p and 4k, and a picture with captions or an overlay is encoded twice at the same CRF. Stated: which faces a caption can be drawn in. Renderers have no DejaVu, Liberation or Noto faces, and a face a renderer lacks is drawn in Helvetica. Stated: Remotion text is drawn heavier than headless Chrome on Linux draws it, and -webkit-font-smoothing: antialiased on the composition draws it lighter.

1.5.3 · 21 November 2026, 17:17 UTC

Job reads carry started_at, when a renderer first took the job, and completed_at, when it reached succeeded, failed, cancelled or expired. Each is null until it happens. Jobs submitted before this change have them too. Stated: updated_at on a finished job is the moment it ended, and nothing changes it afterwards. Stated: a silent or nearly silent timeline mix measures a very low sound.bitrate_kbps.

1.5.2 · 21 November 2026, 16:53 UTC

A webhook endpoint that was removed can be registered again with the same url: it comes back active under the same id, with the new name and events. Only a url that is still active answers 409 webhook_conflict.

1.5.1 · 21 November 2026, 16:47 UTC

A key that passes 120 submits a minute now gets 429 rate_limited with a Retry-After header, the same answer as every other request limit. It used to get 429 request_failed with no time to wait.

1.5.0 · 21 November 2026, 16:45 UTC

A new API reference page: sending a key, a job in three calls with curl, every endpoint, errors, limits and webhooks. The API document names every operation with an operationId and a group, describes the job event a webhook endpoint receives, and lists GET /healthz. GET /v1/usage takes since, until, limit and cursor, and GET /v1/invoices takes limit. GET /v1/jobs/{id}/output answers 409 output_not_ready until a job has succeeded. Corrected: a webhook delivery is sent up to eight times over about 19 hours, not two days. A job.failed for an expired job carries status expired. A removed webhook endpoint stays listed as disabled and its url cannot be registered again. Corrected: creating and revoking keys and adding funds are dashboard calls; a server API key cannot make them. A key may submit 120 jobs a minute. Corrected: FFmpeg, measurement and Remotion work is billed for what the job made, not for processing time. The JavaScript client has wait, services, usage, invoices, me and removeWebhook.

1.4.0 · 21 November 2026, 16:33 UTC

remotion.render.v1 takes x264_preset, x264_profile, b_frames and jpeg_quality, and resolved_props, which returns what a second composition computes in result.resolved_props. Remotion: the page states what a render is when a job sets nothing (CRF 18, x264 preset medium, JPEG frames at quality 80, AAC at 320 kbps, no BT.709 tag unless asked for), which fonts a composition can count on, the browser build, and that a composition loads https media named in its props by itself. Timeline export with picture: copy: what source_url may be, that a source with no sound is accepted and tracks play over silence, that source_audio_url drops the source’s own sound, and that duration_seconds is optional. This list of changes, and a version on the API document that rises with it.

1.3.0 · 21 November 2026, 15:04 UTC

remotion.render.v1 takes sample_rate, 8,000 to 96,000 hertz. The Remotion page describes finishing a render’s sound in a second job: a mov render with pcm-16 sound sent to ffmpeg.timeline_export.v1 with picture: copy.

1.2.0 · 21 November 2026, 14:44 UTC

New services: ffmpeg.frames.v1, ffmpeg.audio.v1 and media.measure.v1. The output link serves jpg and webp files. ffmpeg.transcode.v1 takes start_seconds, duration_seconds, fps, keep_fps_at_least, strip_audio, pad_to_duration_seconds, overlay_image_url, replace_audio_url and replace_audio_in_seconds. Job reads carry failure_message beside failure_code, and failure_code lists every code a buyer can see. A new job reference page: answers at submit, states, charges, failure codes and repeats. The timeline export guide states every behaviour rule: length and padding, encode settings, colour, ducking, sound finishing and what fails an export. Remotion: the renderer opens the bundle from serve_url itself. bundle_manifest_url and bundle_manifest_sha256 are accepted and not used. A repeat compares the whole request, including max_wait_seconds and client_reference. With 8 jobs running, a further submit is refused with 429. There is no verifying job state.

1.1.3 · 21 November 2026, 13:30 UTC

remotion.render.v1 takes input_props_url, still_frame, video_bitrate, encoding_max_rate, encoding_buffer_size, color_space, muted, audio_codec, audio_bitrate, enforce_audio_track, gl, timeout_ms and ignore_certificate_errors. ffmpeg.timeline_export.v1: a video picture segment takes luts. POST /v1/assets takes sha256: the same bytes always get the same link.

1.1.2 · 21 November 2026, 11:20 UTC

New service: ffmpeg.timeline_export.v1. A refused request names up to 100 fields in issues.

1.1.1 · 21 November 2026, 05:07 UTC

Job reads carry output_file, the finished file’s extension and content type, and result, what was measured when the job completed. The output link is kept for 3 days and serves each file under its own type. Every FFmpeg and Remotion input field is in the API document. Media goes by link, up to 1 GB a file.