Delivery by discipline
Conference session video delivery to event organizers.
One film per session, one embed that stays put.
An organizer wants three things from the video team after an event: a player on the event site that shows the event and not a video host, the original files for their own archive, and a way to fix a session when a speaker asks for a cut. Here is a delivery workflow that gives them all three, the plan arithmetic for a real conference, and the one thing it cannot do: gate sessions to ticket holders.
Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month
By uncompressed.io · Updated September 2026
The shape of the delivery
One film per session,
not one programme file.
Upload each talk as its own film. The organizer embeds sessions one by one on the programme page, a speaker asks for changes to one talk and not the others, and captions are checked per speaker. A single long recording of the whole day makes every one of those jobs harder, and a fix to one talk means replacing the whole day.
1
Film on the free plan
Starter holds one film at a time. A programme of sessions needs a paid plan.
1
Embed code per session
It stays the same when you replace the file for a recut.
20 min
Free caption minutes
A month, on Starter. Paid plans are counted in hours.
0
Host logos on the player
The embedded player uses the colours you set, with no uncompressed.io logo.
The workflow
Originals first,
then the embed, then the fixes.
The order matters because of one rule in the product: the download button lives on the watch page, and an Embed only film has no watch page for anyone but you. So the organizer takes the originals before you close the watch pages.
Upload and caption each session
Upload the session export as its own film, set to Unlisted. Generate captions, then correct speaker names, company names and acronyms against the programme before anyone outside the team sees the track.
Hand the organizer the originals
Switch the download on for each session and send the organizer the watch links. They take the original file from each page. No account is needed on their side. The product does not send the links; you do.
Close the watch pages, keep the embeds
Switch each film to Embed only. The watch page now returns not-found for everyone but you, so the download button disappears with it, while the embed on the event site keeps playing. The embed code does not change.
Swap in recuts behind the same code
When a speaker asks for a change, replace the file on that film. The embed on the event site shows the new cut with no edit on the organizer's side. Send the organizer the new original too, since their archive holds the old one.
What the embed can and cannot do
The arithmetic for a real programme
Two meters: storage
and caption minutes.
Streaming carries no per-view charge, so the plan for a conference is decided by two numbers: the total size of the session files and the minutes of captions you generate in the month you deliver. Here is a worked example for a one-day programme of 24 sessions of 45 minutes each, exported at 1080p between 16 and 32 Mbps.
Arithmetic, not a benchmark: bitrate times length, in decimal gigabytes. Your file sizes depend on your export. The 16 to 32 Mbps range is our recommended 1080p review export, not a requirement.
Against the plans: a single 45-minute session at those rates is already about the size of the free plan’s 5 GB, and the free plan holds one film at a time, so Starter is for testing one session with the organizer, not for the programme. Lite ($9 a month) holds 100 GB of streaming storage and 10 hours of captions a month, short on both counts for this example. Pro ($39 a month) holds 500 GB and 25 hours of captions a month, which covers it. Caption minutes are counted per calendar month (UTC), so a programme captioned across a month end draws on two months’ allowance.
If the organizer also wants the camera masters or a mezzanine file for their archive, those do not belong in the embed: browsers do not play most master codecs, and a film holds one main file. Upload a master as its own film with the download on and the visibility set to Password, send the organizer the link and the password, and count its size against the plan too. After the event, a paid plan’s cold archive can hold finished sessions you no longer need to stream; an archived film must be restored before it plays or embeds again.
Captions
A generated track
is a draft until someone checks it.
Conference talks are hard material for speech recognition: speaker names, company names, product names and acronyms, often from the audience microphone. W3C says automatically generated captions do not meet accessibility requirements unless they are confirmed to be fully accurate, and that they usually need significant editing. W3C’s guidance on success criterion 1.2.2, a Level A requirement, also says captions identify who is speaking and include meaningful sound effects, which matters in a panel or a Q&A.
So budget a correction pass per session, working from the programme and the speakers’ slides. The subtitles guide covers the editing order and the export for an organizer who wants caption files for their own platform.
After the event
Same link, same notes:
check what the recut moved.
Speakers ask for changes after the event: a slide with confidential figures, an off-colour remark, a demo that failed. Replacing the file on the existing film keeps the watch link and the embed code, so nothing on the event site changes.
What stays
The film, its link and embed code, its view count, its visibility, the download switch, embed settings, timecoded notes, approvals and captions.
What to check
Kept captions and notes are timed to the old cut. If the recut removes or adds time, regenerate the captions and recheck them. The poster frame is not replaced, so set a new one if the opening changed.
What goes
The previous file is deleted once the replacement is saved. There is no rollback, so keep your own copy of the original cut.
What to send
The organizer's downloaded original is now out of date. Switch the download on again briefly, or send the new file another way, and say which session changed.
The replacement must fit in the plan’s available streaming storage. For the full procedure and how to verify the swap on the live event page, see replace a video without changing its link.
When to use something else
If sessions are a paid product,
this is the wrong tool.
This workflow suits an organizer who publishes sessions on their own site after the event and wants the files. It does not suit an organizer who sells on-demand access: there is no per-attendee login, no ticket check and no password on an embed. If the event already runs on a virtual event platform with gated video, deliver the originals and let the organizer upload them there. And if the goal is the widest possible reach for keynotes after the event, a free public platform such as YouTube does that job without a plan at all; deliver the originals and let the organizer publish.
For a corporate client rather than an event, the same pieces apply with a different cast on the client side; see corporate video delivery to a marketing team.
Questions
Frequently asked
Can I put a password on the sessions and still embed them on the event site?
No. A password-protected film does not play in an embed; the frame shows that the video is unavailable. If only ticket holders should watch, the login has to be the event site's own, and even then the embed address itself is not locked: anyone who has it can open it. For sessions that must stay behind a per-attendee login, use a platform built for gated attendee access.
Will the organizer need an account to download the originals?
No. Viewers never need an account. Switch the download on for the film, send the organizer the watch link, and the watch page shows a download button for the original file. The embed never shows a download button.
A speaker wants a slide blurred after the sessions went live. Does the embed code change?
No. Replace the file on the existing film and the watch link and embed code stay the same, so nothing on the event site has to be edited. The old file is deleted once the new one is saved, so keep your own copy of the original cut.
Can the organizer see who watched each session?
Not by name. The embed records anonymous visitors, counted once per visitor per day, with country, city, device family and the site the embed played on. No names or email addresses are recorded.
Will a session buffer on a slow connection?
It can. The player streams the single file you uploaded; there is no lower-quality copy it switches to. A review-weight export, not the camera master, is the right file to embed, and no bitrate plays smoothly on every connection.
Size the plan to the programme
The free Starter plan holds one film at a time, enough to test one session end to end with the organizer. A full programme needs a paid plan: pick it by the total size of the session files and the caption minutes you need that month.
Sources
- 1.W3C, Understanding Success Criterion 1.2.2 Captions (Prerecorded), Level A: captions identify who is speaking and include meaningful sound effects (fetched 18 September 2026)
- 2.W3C Web Accessibility Initiative, Captions/Subtitles: automatically generated captions do not meet accessibility requirements unless confirmed fully accurate (fetched 18 September 2026)
- 3.uncompressed.io plans: storage, films on the free plan and caption minutes per month (product registry lib/facts.ts) (checked in code 18 September 2026)