LTO Tape Archiving for Productions

Updated October 2026

Native capacities and speeds for LTO-7 to LTO-10 from the LTO Program, which drives read which tapes, how many tapes a project needs, how long the write takes, LTFS, checksums and where tape sits in a 3-2-1 plan.

11 min readIntermediate

LTO-9 and LTO-10
LTFS
Tape count
Checksums

On this page

Why productions archive to tape

Camera originals have to outlive the edit. Hard drives in a cupboard are one option; LTO tape is the usual one for features, series and anything with a delivery or insurance requirement. A cartridge holds tens of terabytes, sits on a shelf with no power, and is a different medium from the drives you edit on, which is what the “2” in 3-2-1 asks for.

The planning questions are arithmetic: which generation, how many tapes, how many hours of writing, and how you will prove the copy matches the original.

LTO-7 to LTO-10 at a glance

Native capacity (LTO Program) and full-height drive speed (IBM)

Generation	Native capacity	Full-height drive	Hours to fill one tape
LTO-7	6 TB	300 MB/s	5.6
LTO-8	12 TB	360 MB/s	9.3
LTO-9	18 TB	400 MB/s	12.5
LTO-10	30 TB	400 MB/s	20.8
LTO-10 (40 TB cartridge)	40 TB	400 MB/s	27.8

Those speeds are for full-height drives, the kind in libraries and larger archive systems. Half-height LTO-7, LTO-8 and LTO-9 drives, the common desktop and Thunderbolt units, run at 300 MB/s native, so a full LTO-8 tape takes 11.1 hours and a full LTO-9 tape 16.7 hours. Check which your drive is before you plan the schedule.

Ignore the compressed figures on the box (45 TB for LTO-9, 100 TB for the 40 TB LTO-10 cartridge). They assume the drive compresses data 2.5 to 1. Camera raw, ProRes, H.264 and H.265 are already compressed, so plan on native capacity and native speed.

LTO-10 comes in two cartridges, 30 TB and 40 TB native; the 40 TB tape uses a thinner aramid base film, and LTO-10 drives take both. An LTO-8 drive can also format an LTO-7 Type M (M8) cartridge to 9 TB native.

Drive and tape compatibility

Up to LTO-7, drives read two generations back and wrote one back. That changed with LTO-8, and it decides how long an archive stays readable on the drives you own.

What each drive reads and writes (LTO Program)

Drive	Reads and writes
LTO-8	LTO-7, LTO-7 Type M, LTO-8
LTO-9	LTO-8, LTO-9
LTO-10	LTO-10 only

New LTO-9 cartridges also need a one-time media optimization on their first load. IBM puts the average at 20 minutes, with some taking up to 2 hours, and advises not to interrupt it. Initialize a batch of tapes before the archive day, not during it. IBM notes it does not apply to LTO-10.

How many tapes you need

Tapes per copy

Tapes = ⌈ Archive size (TB) ÷ (Native capacity (TB) × usable share) ⌉

Leave some of each tape unused: LTFS keeps its index on the tape, and whole files rarely fill a tape exactly. The offload plan in CineMath Professional's Data Planning report counts tapes at 95% of native capacity; use your own figure if your archive software reports one.

Where

Archive size: Everything going to tape: originals, audio, project files, deliverables(TB)
Usable share: Planning allowance, e.g. 0.95

Example: 60 TB feature archive on LTO-9

Calculation:: 60 ÷ (18 × 0.95) = 60 ÷ 17.1 = 3.5
Result:: 4 tapes per copy, 8 for two copies

Tapes per copy for a 60 TB archive, at 95% of native

Generation	Usable per tape	Tapes
LTO-7	5.7 TB	11
LTO-8	11.4 TB	6
LTO-9	17.1 TB	4
LTO-10, 30 TB	28.5 TB	3
LTO-10, 40 TB	38 TB	2

The archive size comes from the shoot: hours of footage times GB per hour for each format, which the free bitrate calculator works out in your browser. The storage planning guide works that through from the shooting ratio.

How long the write takes

Write time

Hours = Archive size (TB) × 10⁶ ÷ Speed (MB/s) ÷ 3,600

Use the slower of the tape drive's native speed and the speed your source can deliver.

Example: 60 TB to a full-height LTO-9 drive at 400 MB/s

Calculation:: 60 × 10⁶ ÷ 400 ÷ 3,600 = 41.7
Result:: 41.7 hours per copy; 83.3 hours for two copies on one drive. On a half-height drive at 300 MB/s: 55.6 hours per copy

Two things stretch that figure. The source must keep up: a single 16 TB hard drive is rated at 240 MB/s, so feeding LTO-9 from it takes 18 × 10⁶ ÷ 240 ÷ 3,600 = 20.8 hours per full tape instead of 12.5. Archive from a RAID or SSD that can sustain the tape's speed. And a verify pass, which reads the tape back to check it, takes about as long again as the write.

Case study

Archiving a feature to LTO-9

Scenario

60 TB of camera originals, sound and project files, two copies on LTO-9 with one going offsite, from a RAID that sustains well above 400 MB/s, with two full-height LTO-9 drives.

Challenge

Know how many tapes to order and how long the drives will be busy, including a read-back verify.

Solution

Work out tapes per copy at 95% of native capacity.
Write both copies at once, one per drive.
Verify each tape by reading it back against the checksums made at offload.

The numbers

Tapes: ⌈60 ÷ 17.1⌉ = 4 per copy, 8 in all
Write: 60 × 10⁶ ÷ 400 ÷ 3,600 = 41.7 h, both copies in parallel
Verify: another 41.7 h per drive, 83.3 h in total

Result

Order 8 tapes (plus spares and time to optimize them), and book about 3.5 days of drive time.

Key takeaways

Native capacity and native speed, never the compressed figures, for camera media.
A second drive halves the elapsed time; a slow source doubles it.

LTFS: tape you can browse

The Linear Tape File System (LTFS) is a SNIA format, published as ISO/IEC 20919, that lets a tape carry its own index of files and folders. Mounted in an LTFS-aware drive, the tape appears as a volume you can browse and copy from, without the backup software that wrote it. That matters for an archive that may be opened years later by someone else with different software.

Tape is still sequential underneath. Reading one clip means winding to it, and copying thousands of small files is slower than copying a few large ones of the same total size. Restore a test file from every tape you write.

Checksums and verification

An archive is only as good as your proof that it matches the originals. Make a checksum of every file at the first offload from the camera card, and check every later copy, tape included, against that same list, not against the copy before it.

ASC MHL, from the American Society of Cinematographers' Motion Imaging Technology Council, records hashes for every copy from the first download to the final archive, as a chain of custody. The reference tool supports MD5, SHA-1, xxHash (xxh64, xxh3, xxh128) and C4.
Keep the hash lists with the media: on the tape itself and in your asset records, so a restore can be checked years later.
Verify by reading back, then log the tape barcode, generation and contents.

Where tape fits in 3-2-1

CISA's 3-2-1 rule asks for three copies of anything important (one primary, two backups), on two different media types, with one copy offsite. A common production layout:

One way to meet 3-2-1

Copy	Medium	Where
Primary	Edit RAID	Edit suite
Backup 1	LTO tape	On site
Backup 2	LTO tape (second set)	Offsite

A RAID counts as one copy however many drives it has; see RAID capacity and rebuild risk. Tape capacities are decimal, so an 18 TB LTO-9 tape shows as 16.37 TiB in tools that count in binary (TB vs TiB).

Next step: size the archive. CineMath's Data & Storage calculator turns a data rate and running time into terabytes; CineMath Professional's Data Planning tool takes a whole shoot, including LTO-7 to LTO-10 storage strategies, and exports the plan as a PDF report.