Petabytes of video.
Frame-accurate. Rights-intact.
Move broadcast libraries between MAM systems, cloud storage, and tape archives without losing a frame, a caption, or a rights record. One logical asset arrives as one logical asset — mezzanine, proxies, every rendition, every language, every sidecar.
- HLS
- DASH
- CMAF · fMP4
- ProRes · DNxHD
- IMF · MXF
- SCC · TTML · WebVTT
Master
source.mov
ProRes 4444 · 4K
tc 01:00:00:00
proxy_h264.mp4
720p editing proxy
hls_master.m3u8
manifest · 6 renditions
audio_en.aac
English audio stem
audio_es.aac
Spanish audio stem
captions_en.vtt
English captions
captions_ja.ttml
Japanese subtitles
thumbnail_4k.png
Poster + keyframes
metadata.xmp
XMP + IPTC sidecar
Why media is different
File migration tools don't survive contact with a broadcast library.
Four constraints make a media migration fundamentally different from moving a folder of documents. Univaultport is designed around all four.
- Generic tools melt
Petabyte-scale mezzanines
A single feature title can be 250 GB before proxies and renditions. A season is multiple TB. A back-catalogue is many PB. Generic transfer tools choke at this scale or cost a fortune in egress.
- Sync breaks downstream
One asset, many files
A single logical episode is master + proxy + HLS ladder + DASH ladder + captions per language + audio stems per language + thumbnails + metadata sidecars. They all have to land together or playback breaks.
- Re-clearances cost months
Rights, captions, MXF metadata
Talent agreements, territory rules, content advisories, music licensing — most of it lives in embedded MXF metadata or sidecar XMP. Lose it on the move and legal review starts over.
- Tooling has to last
Year-long migration windows
Replatforming a broadcast archive is rarely a weekend project. Programs run for 12–18 months with rolling cutovers, parallel ingest, and reconciliation against the old system the whole way.
What travels with the master
Nine artifact categories. All synchronised, all preserved.
Univaultport treats “one episode” or “one feature” as a single logical asset — every related artifact moves with it, and the relationships between them stay intact on the destination.
Mezzanine masters
ProRes 4444 · DNxHR 444 · IMF · MXF OP1a. Frame-for-frame copies. SHA-256 verified after every transfer.
Adaptive bitrate ladders
HLS .m3u8 + every rendition · DASH .mpd + every Representation · CMAF / fMP4 segment maps preserved.
Captions & subtitles
WebVTT · TTML · SCC · iTT · SRT. Per-language, per-region. Timecodes round-trip to the millisecond.
Multi-language audio stems
Dolby Atmos · 5.1 · 2.0 · audio descriptions. Each language as a separate track, all stay aligned.
Posters, thumbnails, keyframes
I-frame strips, sprite-sheet thumbnails, marketing posters at every aspect ratio. Carried with the master.
DRM keys & policies
Widevine, FairPlay, PlayReady policies attach to the asset, not the storage bucket. They migrate together.
Timecode & SCTE markers
Frame-accurate timecode in MXF / MOV containers, plus SCTE-35 ad-break markers and chapter cues.
LTO archive ingest
LTFS-mounted tape volumes streamed into your cloud destination. Verification log per cassette.
Rights & MXF metadata
Embedded MXF metadata + sidecar XMP / IPTC / RDF. Talent, music licensing, territory rules, content advisory.
Inside the ingest
One asset, five stages, zero re-encode.
Mezzanine masters are never re-encoded — they pass through intact, with every related artifact preserved alongside. The whole ingest is observable in real time so your operations team always knows where each title is.
Ingest
Pull from source MAM
Verify
SHA-256 + frame count
Preserve
Metadata + captions + audio
Passthrough
No re-encode · mezzanine intact
Land
Write to destination MAM
Format support
Every container, codec, manifest, and sidecar your library actually contains.
We never re-encode mezzanine masters — every byte passes through intact. The list below is what we recognise and preserve as named artifacts; anything outside this list still moves byte-for-byte as a generic file.
Containers
- MXF· OP1a · OP-Atom · IMF
- MOV
- MP4 · fMP4 · CMAF
- MKV
- WebM
- TS · M2TS
Video codecs
- ProRes 4444 / 422
- DNxHR / DNxHD
- H.264 / AVC
- H.265 / HEVC
- AV1
- JPEG 2000 · IMF
Audio codecs
- PCM
- AAC
- Dolby Digital Plus
- Dolby Atmos · ADM BWF
- MP3
- Opus
Manifests
- HLS · .m3u8
- DASH · .mpd
- CMAF
- Smooth Streaming
- Live → VOD relays
Captions
- WebVTT
- TTML / IMSC
- SCC · CEA-608/708
- iTT
- SRT · DFXP
Sidecar metadata
- XMP · IPTC
- RDF · JSON-LD
- EBUCore · PB Core
- SMPTE 380M (MXF descriptive)
Ecosystem
Talks to the stack you already operate.
MAM systems, hyperscaler storage, OTT delivery, post-production, and tape archives. Native connectors for the widely-deployed platforms; custom connectors for anything else, including legacy and in-house systems.
Custom MAM connectors
In-house MAMs, regulated cloud, broadcast TX systems. Share the API contract — we ship a production connector in 2–4 weeks with the same observability as our native ones.
MAM platforms
Iconik
● native
Cantemo
● native
Dalet Galaxy
● native
Avid Nexis
● native
EditShare EFS
● custom
Vidispine
● custom
Cloud storage
Amazon S3
● native
S3 Glacier
● native
GCS · Coldline
● native
Azure Blob · Archive
● native
Backblaze B2
● native
Wasabi
● custom
OTT & delivery
Brightcove
● native
JW Player
● native
Mux Video
● native
AWS MediaPackage
● native
Cloudflare Stream
● native
Editorial & post
Adobe Premiere
● native
Adobe AEM Assets
● native
Avid Media Composer
● custom
DaVinci Resolve
● custom
Archive & tape
LTO via LTFS
● native
Quantum Scalar
● custom
StorageDNA
● custom
Reference scenario
A national broadcaster's 3.2 PB cloud journey.
A representative end-to-end engagement. Numbers below match the median of broadcaster-scale migrations we've sized; the narrative is a composite, not a specific customer.
“The metadata round-trip is what closed it for us. Our legal team didn't have to revisit a single rights record after the cutover — that turned a six-quarter program into a one-quarter program.”
Head of Media Operations · National broadcaster · EMEA
0 PB
archive migrated
0
episodes + features
0 languages
caption coverage preserved
0%
asset-level success rate
Cutover window
14 weeks
rolling, with parallel ingest from week 4
Frame accuracy
100%
mezzanines passed through · no re-encode
Rights records
0 lost
MXF metadata + sidecars preserved byte-for-byte
Re-clearance work
eliminated
all music + talent records carried with the master
Frequently asked
What broadcast ops teams always ask first.
Book a media migration call
Map your library with a media solutions architect.
30 minutes. We sketch your source → engine → destination flow on the call, pick the right preservation strategy for your catalogue, and you leave with a written architecture either way.
- Connector compatibility map for your MAM + storage stack
- Media playbook + format support matrix emailed after the call
- Reconciliation strategy against your existing MAM
- Honest fit assessment — we say no if we are not the right tool
Move the library.
Keep the metadata.
A 30-minute call with a media solutions architect. Bring your library spec; leave with a written migration plan you can hand to your CTO.
Univaultport for Media & OTT · Frame-accurate. Rights-intact.