Teradek and Frame.io Camera to Cloud: Serv, Prism, Core, and S3 explained
Understand what Teradek Serv and Prism upload, how Core and Teradek TV differ, and when Frame.io, PIX, Sony Ci, or custom S3 receives the file.
The short answer
Teradek Serv and Prism can encode a recording from a camera’s HDMI or SDI output and upload that file. Serv 4K and Prism document Frame.io, PIX, Sony Ci, and custom S3 destinations; Serv Micro is currently documented with Frame.io. Core manages and routes Teradek devices and live feeds, while Teradek TV is a secure monitoring environment.1,2,4,5
Teradek creates a new network-ready recording from video output.
Serv and Prism sit between the camera output and the network. They do not read the camera card; they encode and record the HDMI or SDI signal, then upload that recording. This broadens camera compatibility, but the cloud file is a new representation rather than the internal camera original.
Serv can trigger recording manually, from a compatible camera event, or from a streaming event. Teradek documents sequential or parallel uploads and retains recordings on the device for local access.2,3
| Product | Primary role | File destination | Live role |
|---|---|---|---|
| Serv 4K | On-set encoder, recorder, and viewer | Frame.io, PIX, Sony Ci, custom S3 | Local/remote monitoring and streaming |
| Serv Micro | Compact on-set encoder, recorder, and viewer | Frame.io is currently documented | Local/remote monitoring and streaming |
| Prism family | Broadcast-oriented encode and record | Frame.io, PIX, Sony Ci, custom S3 | Core-managed contribution and distribution |
| Core | Device management, bonding, and routing | Coordinates device workflows | Routes live feeds |
| Teradek TV | Secure production monitoring and review | Recordings within monitoring workflow | Managed viewers, comments, and live feeds |
A viewable proxy is not automatically a relinkable proxy.
For offline/online editing, verify clip name, timecode, record trigger, frame rate, and head/tail behavior for the exact camera-device pair. Frame.io’s workflow guidance makes those fields central to relinking and warns that external-recorder timing can differ.6,7
Off-speed footage deserves a dedicated test because a real-time SDI/HDMI recording may not reproduce the camera’s internally interpreted high-frame-rate file.
Use external hardware when the production needs more than a native upload menu.
Teradek is especially useful when the source camera lacks native cloud upload or the production also needs client monitoring, managed viewers, bonded connectivity, or live distribution.
Choose native camera upload
When the camera creates the exact proxy/original you need and the chosen destination is supported.
Choose Serv
When a compact camera-side monitor/encoder can solve file upload and on-set viewing.
Choose Prism/Core
When the job needs broadcast routing, multiple encoders, bonding, or managed live contribution.
Budget the rig
Account for power, media, cabling, mounting, networking, firmware, and metadata validation.
Frequently asked questions
Does Teradek upload the original camera file?+
Normally it records the camera’s HDMI or SDI output and uploads that new encoded file. That is different from reading the internally recorded camera original.
Can Teradek Camera to Cloud upload somewhere besides Frame.io?+
Yes on documented Serv 4K and Prism workflows, which list PIX, Sony Ci, and custom S3 alongside Frame.io. Do not assume every destination applies to Serv Micro; its current guide verifies Frame.io.2,4
Is Teradek Core the same as Frame.io?+
No. Core manages Teradek devices, connectivity, and live routing. Frame.io is a file collaboration and review destination. A workflow can use both.
Sources
Sources were last reviewed on . Vendor interfaces and documentation can change; follow the linked source and re-test the exact production workflow.
- 01TeradekServ product family ↗
- 02
- 03TeradekServ recording guide ↗
- 04
- 05TeradekTeradek TV workflow ↗
- 06Adobe Frame.ioGetting started with Camera to Cloud ↗
- 07Adobe Frame.ioComplete Camera to Cloud proxy workflow ↗