Av1

Use the bitrate calculator to size the workload, or build your own licence with Callaba Self-Hosted if the workflow needs more flexibility and infrastructure control. Managed launch is also available through AWS Marketplace.

What it means

AV1 is a modern video codec with strong compression efficiency, especially for VOD and bandwidth-sensitive delivery. Benefits depend on workload and hardware/software decode support. For this workflow, Ingest & route is the most direct fit.

Decision guide

1. Segment traffic by device decode capability.
2. Choose AV1 for VOD-first or premium paths initially.
3. Keep AVC fallback for broad compatibility.
4. Model encoding time and infra cost before rollout.
5. Canary release with clear rollback criteria.

Implementation stack: Video platform API, Player and embed, and 24/7 streaming channels.

Latency budget and architecture budget

• Encode time impact is primary AV1 constraint for live.
• Packaging and delivery stay similar with HLS/CMAF.
• Player decode path must be validated per device class.

Reference: bitrate strategy, resolution planning.

Practical recipes

Recipe 1

1. Start AV1 on VOD catalog for high-traffic assets.
2. Keep AVC fallback manifests.
3. Compare completion and startup by device cohort.

Recipe 2

1. Enable AV1 for selected geos with expensive bandwidth.
2. Track egress savings vs encode spend.
3. Adjust ladder values for balanced QoE.

Recipe 3

1. For live pilots, use limited concurrency and strict SLA monitoring.
2. Avoid full migration until encode performance is proven.
3. Automate profile routing through API policy.

Practical configuration targets

• Keep AV1 ladders conservative initially.
• Maintain 30-45% ABR steps.
• Retain AVC default for unsupported devices.

Limitations and trade-offs

• Higher encode complexity and cost.
• Inconsistent device support across older hardware.
• Live low-latency AV1 can be operationally expensive.

Common mistakes and fixes

• Mistake: AV1-only rollout. Fix: dual codec delivery.
• Mistake: no cohort segmentation. Fix: track by decode capability.
• Mistake: ignoring encode SLA. Fix: monitor queue and encode duration.

Rollout checklist

• Device matrix validated.
• AVC fallback guaranteed.
• Cost/perf dashboard ready.

Example architectures

Dual-codec VOD delivery with API-driven manifest policy is a practical AV1 adoption model.

Troubleshooting quick wins

1. Startup regressions: inspect device decode and manifest selection.
2. Cost spikes: limit AV1 to high-value assets.
3. Queue growth: split AV1 and AVC processing pools.

Next step

Continue with resolution strategy, bitrate tuning, and Video platform API.