Every meeting that's streamed live also produces a recording automatically. For meetings that aren't streamed (or where the stream failed), you can upload a recording manually afterward. Either way, the Media tab is where the recording ends up, and it's where you'll go to verify it processed correctly, troubleshoot if processing failed, and access the playback experience that surfaces transcripts and timestamps.
This article covers the recording side of the Media tab: how recordings get there, what processing looks like, what to do when an upload fails, and the basic playback layout. The deeper AI features (transcripts, timestamps) are covered in Transcripts and Timestamps.
Where to find it
On any meeting page, click the Media tab.
[IMAGE: The Media tab showing the recording-related panels]
The Media tab requires the Recording module (hasRecord flag). The recording features here don't additionally require the streaming flag — uploads work even when streaming is disabled.
How recordings get to the Media tab
A recording can arrive in the Media tab two ways:
From a live stream
If your meeting was streamed live (see Streaming the Meeting Live), the encoder created a recording archive automatically when the stream ended. The recording appears in the Media tab within a few minutes after End Meeting.
You don't need to do anything to "save" the recording — it's saved automatically as the stream runs. The Media tab will show "Processing Recording" while the post-stream processing finishes, then transition to playback once the recording is ready.
From a manual upload
For meetings that weren't streamed, you can upload a recording file directly. The Media tab will show a No Recording Available zero state with an Upload Recording button.
[IMAGE: The No Recording Available zero state with the Upload Recording button]
Click Upload Recording to reveal the upload form.
Uploading a recording
The upload form supports drag-and-drop or click-to-select for video files.
[IMAGE: The recording upload form with the drag-and-drop area]
Supported formats and sizes
Govinity uses Mux for video processing, which supports a wide range of input formats:
Video codecs: H.264, H.265 (HEVC), VP9, AV1, ProRes, and many others.
Container formats: MP4, MOV, MKV, AVI, WebM, FLV, and others.
Audio codecs: AAC, MP3, Opus, FLAC, PCM, and others.
Most modern recordings (from cameras, phones, or screen recorders) work without conversion.
For best results: - H.264 video + AAC audio in an MP4 container is the most reliable format. - No specific maximum file size is enforced in the UI — Mux can handle large files, but uploads of multi-hour 4K recordings will take a while.
What happens during upload
The form opens a direct upload to Mux (Govinity's video processing partner) — your file goes straight from your browser to Mux storage. Govinity tracks progress and triggers processing once the upload completes.
After upload finishes, the UI polls every 2 seconds for up to 30 seconds to confirm the archive record was created on the Govinity side. You'll see:
A progress bar during upload.
A "Processing" state once upload completes.
A toast: "Upload complete. Your media is being processed."
The processing state
Once a recording exists (from either streaming or upload), Mux processes it — generating playback streams, thumbnails, and the data needed for video player features. While processing runs, the Media tab shows a "Processing Recording" panel with a spinner.
[IMAGE: The Processing Recording panel with a spinner]
Processing time varies:
Short recordings (under an hour): typically 1-5 minutes.
Long recordings (multi-hour meetings): 10-30 minutes.
Very long recordings or unusual formats: sometimes longer.
The Media tab polls every 5 seconds while processing. Once Mux finishes, the page automatically updates to show the playback view.
You don't have to keep the tab open — processing continues server-side regardless. Come back when you're ready and it'll be done.
When processing fails
Sometimes processing fails — usually because of an unsupported codec, a corrupted file, or a recording that didn't get properly closed (common with crashed encoders).
[IMAGE: The Upload Failed error state with the Start Over button]
When this happens, the Media tab shows an Upload Failed error state with:
The specific error message from Mux (e.g., "The file could not be decoded," "Unsupported codec").
A Start Over button.
Click Start Over to:
Delete the failed archive from Govinity.
Return the Media tab to the No Recording Available state.
Show the Upload Recording button again.
You can then try uploading a different file — often the fix is re-exporting from your video editor with a more standard codec, or trying the original file again after a fresh export.
If the same file fails repeatedly, the issue is likely the file itself. Try a different recording or contact Govinity support.
The playback view
Once processing completes, the Media tab shows the recording in a two-column playback view:
[IMAGE: The recording playback view with the left content panel and the right video sidebar]
Left column (about 70% width) — contains sub-tabs for Transcript and Timestamps, each with their own content. Covered in detail in Transcripts and Timestamps.
Right column (about 30% width) — the persistent video sidebar showing the recording player.
The video sidebar stays visible as you scroll or switch sub-tabs, so you can always see the video while reading the transcript or scanning timestamps.
The video sidebar
The sidebar includes:
The Mux video player with standard controls (play/pause, scrubber, volume, fullscreen, playback speed).
A settings button that opens the Recording Settings sheet (covered next).
The current playback time, which is shared with the left-column tabs (e.g., a "Set" button on the Timestamp form can grab the current playback time for a new timestamp).
The Recording Settings sheet
Click the settings icon in the video sidebar to open the Recording Settings sheet — a side-panel where you can configure how the recording appears across Govinity and the public portal.
[IMAGE: The Recording Settings sheet showing the thumbnail configuration options]
The settings include:
Thumbnail frame time — picks a specific timestamp in the video to use as the thumbnail (e.g., "5 minutes in"). Useful when the start of the recording is a blank screen and you want to show the meeting in progress.
Upload custom thumbnail — replace the auto-generated thumbnail with your own image (e.g., a meeting body's logo, a "Meeting in Progress" graphic).
Audio-only — toggle to mark the recording as audio-only. The public player will surface audio controls without expecting video. Use for podcast-style recordings or meetings recorded without a camera.
Changes save immediately when made and apply across all surfaces where the recording is shown.
What the public sees
Once the recording is processed and the meeting is no longer marked private:
The meeting's public portal page shows the recording embedded as a video player.
Citizens can play, scrub, change speed, and view fullscreen.
The thumbnail you configured appears in any link previews or social media shares.
The transcript (if generated) appears as a clickable list below the video — clicking a transcript segment seeks the video to that point.
For private meetings, the recording is stored but not surfaced publicly. Only staff with access to the meeting can play it.
Replacing a recording
You can replace a recording at any time:
From the playback view, click the trash icon on the existing archive (this may live in the Recording Settings sheet depending on layout).
Confirm deletion.
The Media tab returns to the No Recording Available state.
Upload a new recording.
Replacing is sometimes useful when:
A re-edited recording is more polished than the raw stream.
The original was corrupted.
An audio-only version is preferred to the video version.
Be cautious: replacing wipes any AI-generated transcripts and timestamps tied to the old recording. You'd need to regenerate those for the new file.
Common questions
My recording is too large to upload from my computer. The upload is direct to Mux storage, not through your local network bottleneck — but it does go through your browser. For very large files (multi-gigabyte 4K recordings), try uploading from a connection with high upload speed. If the upload keeps timing out, contact Govinity support — there may be a back-channel upload path.
Can I edit the recording within Govinity (trim, crop, etc.)? No. Govinity stores and plays recordings; editing happens in your video editor before upload. For trimming, common approach: trim in iMovie / DaVinci Resolve / Premiere, export an MP4, upload.
What if I have two recordings (different camera angles)? Govinity stores one recording per meeting. You'd need to combine angles in a video editor and upload the combined file, or pick one angle and stick with it.
Can I download the recording from Govinity later? Yes — there's typically a download link in the playback view. The download is the Mux-hosted file in MP4 format.
How long does Govinity keep recordings? Indefinitely. Storage costs are part of your subscription. If you have very large recording libraries and need to manage storage, reach out to your account team.
Can I make a recording private after it was public? Mark the meeting as private (Edit Meeting → Private Meeting toggle). The recording is private as long as the meeting is.
What this article doesn't cover
Live streaming — see Streaming the Meeting Live.
Transcripts and timestamps — see Transcripts and Timestamps.
Encoder configuration — see Setting Up Live Streaming for Your Government (admin).
The public portal video player — see public portal documentation.
What to read next
Transcripts and Timestamps — the AI features that make recordings searchable and navigable.
Auto-Generated Meeting Documents — how recordings interact with the Documents tab.
Streaming the Meeting Live — for the live-streaming path.
Need help?
If a recording uploads but never processes, check that the file is a valid video format (try opening it locally first). If processing fails repeatedly with the same error, the file likely has a codec issue — try re-exporting from your video editor. For anything else, reach out to Govinity support.
