Convert anything, at global scale.
200+ formats and automation APIs that feels instant.
CONVERT
From
To
IIQ at a glance
IIQ
Phase One positioned IIQ around its medium-format and digital-back workflows, which is why IIQ appears in a very different professional context from ordinary consumer camera raws.
TS at a glance
TS
Transport streams belong to the broadcast and transmission side of digital video history, where resilience and streaming mattered more than user-friendly file semantics.
Format comparison
| Feature | IIQ | TS |
|---|---|---|
| File type | Image | Video |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 2007 | 1995 |
| Inventor | Phase One | Moving Picture Experts Group (MPEG) |
| Status | proprietary | active |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not supported | Not supported |
| Camera raw data | Supported | Not supported |
| HDR support | Not supported | Not supported |
| Streaming ready | Not supported | Not supported |
When to use each format
When to use IIQ
- Your source file is already in IIQ.
- Preserve source expectations before exporting to TS.
- IIQ is commonly used in image workflows.
When to use TS
- Your target workflow expects TS.
- Improve delivery compatibility with TS.
- TS is commonly used in video workflows.
FAQs
Why convert IIQ to TS?
Convert to TS when the destination expects transport streams, such as broadcast workflows, segment-based media handling, receiver recordings, or other systems where packetized streaming compatibility matters.
It is useful as an operational and interchange format inside media infrastructure.
For easier library playback and casual sharing, MP4 or MKV are usually more convenient.
What changes when converting IIQ to TS?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to TS removes camera raw data.
What should I review after converting IIQ to TS?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.