Frame interpolation as a REST API.
Presign upload, probe the video, create a target-FPS job, then poll status until the output is ready.
For developers adding smoother video output to their own media pipelines.
Upload a clip120 trial xeconds · No card · Watermarked preview
ReframeFX fills the gap between captured frames.
Direct answer
What this workflow covers.
Use pricing endpoints to estimate charged xeconds before creating a render job.
Upload through a signed URL, then let the backend probe FPS, duration, resolution, and codec.
Create target-FPS jobs and poll structured live_status values until the output is ready.
How it works
The frame interpolation API flow
The API follows the same observable workflow as the browser studio and uses the same xeconds balance, so cost and status stay consistent across both surfaces.
- 01
Create a signed upload
Request an upload URL and send the video directly to object storage without proxying the media through your application server.
- 02
Probe and estimate
Read server-verified video metadata and request target-FPS estimates before creating a paid job.
- 03
Create and poll the job
Submit the chosen target FPS, then poll structured status values until the output is ready or the job fails and is refunded.
FAQ
Useful answers, without the filler.
What is frame interpolation api in ReframeFX?
Presign upload, probe the video, create a target-FPS job, then poll status until the output is ready.
Does ReframeFX show the cost before rendering?
Yes. ReframeFX charges whole input seconds at the target-FPS band: 1× up to 60fps, 2× for 61–120fps, and 4× for 121–240fps.
Can I use ReframeFX without installing desktop software?
Yes. ReframeFX is a browser and API workflow for cloud frame interpolation.
Does the API use a separate balance?
No. Browser and API jobs use the same xeconds balance and the same target-FPS pricing rules.