Check a real recording.
Test a new upload, repeat playback, and seeks into later parts of a long video on desktop and mobile.
FOR NEWSROOMS, PUBLISHERS & PUBLIC ARCHIVES
Keep the whole story.
Including the video.
Make room for council meetings, public events, interviews, and the recordings behind your reporting. Your article can stay small while its source material stays available.
AN EXAMPLE LOCAL NEWS WORKFLOW
This week’s meeting.
Next year’s reference.
A local newsroom publishes a recording next to its meeting coverage. Most people watch soon after publication. Months later, a reader follows the same link to check what was said.
An illustrative workflow, not a customer testimonial or a measured traffic forecast.
- Prepare a web-friendly copy of the recording
- Upload it and verify playback
- Embed the player in the article
- Keep the source address with the story
A TYPICAL VIEWING PATTERNILLUSTRATIVE
NEWLY PUBLISHEDOLDER ARCHIVE
Your library keeps growing. Attention often moves on. Repeated requests can be served from cache while the full archive remains in storage.
PLAN THE LIBRARY AND THE AUDIENCE
A few numbers.
A clearer storage plan.
Estimate file size, monthly delivery, and the cost of delivery above Publish’s included 3 TB. This is a planning estimate, not a bill or a prediction of cache performance.
NEW STORAGE EACH MONTHESTIMATED MONTHLY DELIVERYESTIMATED ADDITIONAL DELIVERY COST
$2 per additional TB above 3 TB per month, excluding the $10 subscription. Additional delivery requires opt-in and a monthly spending limit. The previous month’s actual additional delivery is added to your next monthly bill; outstanding usage is settled when your subscription ends.
Twelve months of these uploads add about 291.6 GB. Existing files, extra renditions, container overhead, and other downloads are additional.
Estimates use decimal GB and TB. A full-length equivalent view is the total watched time divided by the recording’s duration. Cached views still count as delivery. Cost estimates use only bytes above 3 TB, without rounding up to whole TB. Publish uses decimal TB, matching these estimates. Keep and Free use binary GiB and TiB.
BEFORE YOUR NEXT BIG PUBLISHING DAY
Test the workflow
you actually use.
Allow for the busy week.
Compare your stored library and total delivered bytes with the plan’s limits. A predictable average does not eliminate peaks.
Connect your tools.
Start with browser uploads. Use the documented API when your publishing volume calls for a repeatable integration.
Larger custom quotas, guaranteed cache windows, transcoding, multi-user roles, and service-level commitments are not included in the advertised plans. Confirm the required workflow before relying on them.
Let your archive grow.
Keep your publishing simple.
Review the current Publish plan and its delivery limits.