Recording Storage for BigBlueButton: Retention, Cost, and Speed
Everything IT teams and institution administrators need to know about managing BigBlueButton recording storage — from how recordings are generated and what they cost to store, to retention policies, S3 extension options, download speed, and how BiggerBluButton's managed infrastructure handles it all without disk-space emergencies. Recording storage is the silent cost that every BigBlueButton deployment eventually collides with — and almost no institution plans for it correctly at the outset. A single one-hour BigBlueButton session generates between 200 MB and 800 MB of stored data depending on which recording formats are enabled. Multiply that across a semester of daily lectures, lab sessions, and office hours across dozens of courses, and you are looking at terabytes of accumulated recording data that need to be stored reliably, served quickly, governed by a retention policy, and backed up without fail. This guide covers everything IT administrators, instructional technology teams, and institution procurement leads need to know about BigBlueButton recording storage: how recordings are generated and what post-processing produces, how much storage each format consumes, how to model your institution's storage needs before you run out of space mid-semester, what retention policies should look like, how S3-compatible extended storage works on BiggerBluButton, and how recording playback speed and download performance are affected by your hosting infrastructure. We also address the full recording workflow — how to record BigBlueButton meetings, how to access BigBlueButton recordings after a session, how to download recordings from BigBlueButton as MP4, how to save recordings from BigBlueButton to external systems, and how to share recordings with students in Canvas or Moodle. Every step in that workflow is affected by how your storage layer is configured and sized. For institutions on BiggerBluButton managed hosting, the storage architecture is already designed, backed up daily, and extensible on demand at $0.022 per GB — with plans ranging from 100 GB (Personal) to 30 TB (Enterprise-3). For self-hosted deployments, this guide provides the planning framework to avoid the most common and most disruptive storage failure mode: a full disk that silently aborts recording post-processing mid-session. Quick Navigation Understanding why BigBlueButton recording storage is a genuine planning challenge requires understanding what actually happens between the moment you click "End Session" and the moment a student clicks play on a recording in Canvas. The storage journey has four distinct phases — and each one consumes disk space that must be provisioned in advance. During the session, BigBlueButton captures raw event logs, audio streams, video streams, whiteboard events, and chat in separate unprocessed files in After the session ends, BigBlueButton's recording processor converts raw files into the configured formats (Presentation, Video, Podcast). Processing is CPU and disk-intensive — a 1-hour session can take 30–120 minutes and requires significant temporary disk space in Processed recordings are moved to BiggerBluButton generates downloadable MP4 files from processed recordings — an additional file that provides offline access and is compatible with any video platform. MP4 export adds to total storage consumption but is managed within the plan's included storage allocation. The critical operational risk for self-hosted BigBlueButton: if the server's disk fills up at any point during Phases 1–3, the recording job silently fails. There is no end-user error message — the session appears to end normally, but the recording never appears in the Recordings tab. This is one of the most common support escalations for self-hosted BigBlueButton and the primary reason proactive storage planning is essential. BiggerBluButton eliminates disk-full recording failures: recordings are processed on managed infrastructure with scalable cloud storage, daily backups, and storage alerts built into the platform. Your recordings never disappear due to a full server disk. BigBlueButton recording storage and hosting infrastructure are inseparable planning concerns. The server that runs your live sessions is also the server that processes recordings — and recording post-processing competes directly with live sessions for CPU, RAM, and disk I/O. Institutions that size their server for live-session capacity without accounting for recording storage and post-processing load routinely experience two compounding problems: recording jobs that take hours longer than expected because they are competing with live sessions, and disks that fill up mid-semester because no one calculated the actual storage growth rate. On BiggerBluButton's managed network, recording storage is architected separately from live-session compute. Recordings are processed and stored on dedicated storage infrastructure — not on the same disk as the active session server. This means: Every BiggerBluButton plan includes a defined storage allocation for recordings. The smart load balancer across data centres in Germany, USA/Canada, Singapore, and India also ensures that recording playback is served from a region geographically close to your users — reducing playback buffering and improving perceived download speed for students accessing recordings after class. When included storage is exhausted, S3-compatible extended storage is available at $0.022 per GB — added directly from the BiggerBluButton dashboard without any server configuration, downtime, or migration process. This is particularly relevant for institutions mid-semester that miscalculated their storage needs — the extension is instant. BiggerBluButton provides three native BigBlueButton recording formats plus MP4 download. Each format has a dramatically different storage footprint — understanding the differences is essential for accurate storage planning. The figures below are based on a standard 1-hour session with one presenter, one shared screen, and 20–30 participants with webcams enabled. Enabling all three formats simultaneously multiplies storage consumption approximately 3–4× compared to Presentation-only. For a university running 50 one-hour recorded sessions per week: Estimates based on typical 1-hour lecture sessions with shared slides and audio. Video-heavy sessions (webcams + screen share) will be at the higher end of ranges. Podcast and Presentation formats are at the lower end. Every BiggerBluButton plan includes a defined recording storage allocation. The table below maps each plan's storage to the recording volume it can realistically support, based on Presentation-format recordings (the most common and most efficient format for academic use). S3 Extension: When any plan's included storage is exhausted, additional capacity is available at $0.022 per GB — added instantly from the BiggerBluButton dashboard. No server reconfiguration, no downtime, no migration. For reference: 1 TB of additional S3 storage costs approximately $22.53/month at that rate, making it very cost-effective for institutions with variable recording volumes across the academic year. The most accurate way to estimate your BigBlueButton recording storage needs is to work from your actual teaching calendar — not from headline numbers like total enrolled students. Here is a step-by-step planning framework that gives you a realistic semester-end storage forecast. Count the number of BigBlueButton sessions per week that will have recording enabled. Be specific: separate lectures (likely all recorded), labs (partially recorded), and office hours (rarely recorded). Add these up for a weekly recorded-session total. Example: 40 lectures/week + 15 recorded labs/week + 5 office hours/week = 60 recorded sessions/week. Most university sessions are 50–90 minutes. Training sessions may be 2–4 hours. Use your real average, not a round number. Example: Average session = 75 minutes (1.25 hours). Formula: Weekly sessions × Session duration (hrs) × GB/hr × Semester weeks = Total storage needed Example: 60 sessions × 1.25 hrs × 0.35 GB/hr × 16 weeks = 420 GB per semester. This fits within a Bronze plan (500 GB) for Presentation-only. If you keep recordings for two semesters before deletion, you need ~840 GB → upgrade to Silver (750 GB) + some S3 extension, or Gold (1 TB). Storage is only half of the recording equation. How quickly recordings load in the browser, how smoothly they play back, and how fast the MP4 download completes are all directly affected by your hosting infrastructure — and they are the performance metrics that students and instructors actually experience every day. A retention policy defines how long BigBlueButton recordings are kept before they are deleted. Without a defined policy, recordings accumulate indefinitely — consuming storage that grows without bound, creating FERPA and GDPR exposure for institutions that retain identifiable student data longer than necessary, and making it increasingly difficult to manage recording libraries at scale. Full data governance policy and privacy terms: biggerbluebutton.com/terms-and-conditions · biggerbluebutton.com/privacy-policy The recording workflow on BiggerBluButton covers everything from initiating a recording during a live session to managing the stored recording archive weeks later. Here is the complete operational guide — structured for IT administrators and instructors. Full recording API documentation: docs.biggerbluebutton.com/api/reference · Recording format docs: docs.biggerbluebutton.com/recordings/podcast When BigBlueButton is integrated with Canvas via LTI 1.3, recording storage and LMS access are directly linked. The quality of your storage infrastructure affects how quickly recordings appear in Canvas course pages, how reliably they play back for students, and whether the recording links remain stable across the academic year. Can students record Canvas conferences in BigBlueButton? No — only moderators (instructors via LTI role mapping) can initiate recording on BigBlueButton. Students joining via Canvas as Learners/Viewers do not see recording controls and cannot start, pause, or stop the recording. The moderator controls the entire recording lifecycle — including which recordings are published and accessible in the Canvas Recordings tab. The following BiggerBluButton resources are directly relevant to recording storage planning, capacity sizing, retention management, and performance optimisation. Storage consumption depends heavily on which recording formats are enabled and how video-heavy the session is. A 1-hour session in Presentation format (slides + audio) uses approximately 150–400 MB. The same session in Video format (all webcams + screen share + audio) uses 500 MB to 2 GB. Podcast format (audio only) uses just 30–80 MB. Enabling all three formats for every session multiplies your storage consumption 3–4× compared to Presentation-only. BiggerBluButton plans range from 100 GB (Personal) to 30 TB (Enterprise-3), with S3 extension available at $0.022 per GB for any plan. Log in to your BiggerBluButton dashboard and navigate to the Recordings section. All completed recordings appear here with their format, file size, date, duration, and status. Post-processing typically takes 30–90 minutes for a 60–90 minute session — recordings with "Processing" status are not yet available for playback. Once status shows "Available," you can play, share, publish, or download the recording as MP4 directly from the dashboard. If you use Canvas LTI integration, recordings also appear automatically in the Recordings tab of the BigBlueButton LTI activity inside your Canvas course. In your BiggerBluButton dashboard Recordings section, click the MP4 download icon next to any completed recording. BiggerBluButton generates and serves the MP4 file from the nearest regional storage node — download speeds are typically 20–100 Mbps, making a 500 MB MP4 download complete in under 60 seconds for most users. The MP4 file is compatible with any device, video player, LMS media embed, or external platform. MP4 download is available on all BiggerBluButton plans, including the Free plan within its 1 GB storage limit. BiggerBluButton sends storage alerts before your allocation is exhausted — you will not wake up to a full-disk surprise. When you approach your plan's storage limit, you can extend instantly at $0.022 per GB from the dashboard — no server reconfiguration, no downtime, no migration. Unlike self-hosted BigBlueButton where a full disk silently aborts recording post-processing jobs with no user-visible error, BiggerBluButton's managed storage layer handles capacity limits gracefully with alerts and on-demand extension. With LTI 1.3 integration, recordings from Canvas-launched sessions appear automatically in the Recordings tab of the BigBlueButton activity inside the Canvas course — no manual sharing step needed. To share a recording manually (for example, to a different Canvas course), copy the playback URL from your BiggerBluButton dashboard Recordings section and paste it as a Canvas Page external URL or Module item. Ensure the recording's visibility is set to "Published" in your dashboard before sharing any direct link. To send a BigBlueButton video recording to Canvas as an MP4, download it from the dashboard and upload it to Canvas Studio or embed it via the Media Library. BiggerBluButton maintains daily backups of all recordings across the managed infrastructure. Daily backup cadence means that in the unlikely event of a storage issue, data loss is limited to at most one day's worth of newly processed recordings. Backup restoration is handled by the BiggerBluButton team — account holders do not need to manage or initiate backup processes themselves. This is a significant operational advantage over self-hosted BigBlueButton where backup configuration, scheduling, and testing are entirely the responsibility of the institution's IT team. No — students cannot initiate recording on BigBlueButton. The Canvas LTI integration maps students to the Viewer/Learner role, which has no access to recording controls. Only instructors in the Moderator role can start, pause, stop, or end a BigBlueButton recording. This role-based access control is enforced automatically through LTI role mapping — no per-session configuration is needed. If a teaching assistant needs recording access, the instructor must manually promote them to moderator within the active session. For 50 Presentation-format sessions per week averaging 75 minutes each, the storage growth rate is approximately 13–17 GB per week, or 210–270 GB per 16-week semester. For single-semester retention, the Bronze plan (500 GB, $39.9/month) comfortably covers this workload. For two-semester retention before deletion, upgrade to the Silver plan (750 GB, $54.99/month) or Gold plan (1 TB, $59.99/month). If you enable all three recording formats (Presentation + Video + Podcast), storage consumption jumps to approximately 700 GB per semester — requiring at minimum a Gold or Platinum plan, or Bronze with S3 extension at $0.022/GB. All plans include a 7-day free trial. Full plan details at: biggerbluebutton.com/plans BiggerBluButton's managed recording storage handles growth automatically — scalable cloud storage, daily backups, multi-region playback speed, and instant S3 extension at $0.022/GB. Plans from $7.99/month with 7-day free trial on all paid tiers. 100 GB – 30 TB included · 99.9% Uptime SLA · MP4 Download · All 3 Recording Formats · VIP Support on Enterprise
BigBlueButton Hosting · A004Recording Storage for BigBlueButton: Retention, Cost, and Speed
How BigBlueButton Recordings Are Generated, Stored, and Structured
/var/bigbluebutton/recording/raw/. This raw data is typically 2–5× the size of the final processed recording./var/bigbluebutton/recording/process/./var/bigbluebutton/published/ and become accessible via the playback URL. This is the storage footprint that grows indefinitely unless a retention policy removes older recordings. On BiggerBluButton, published recordings are served from governed cloud storage — not local disk.Recording Storage and BigBlueButton Hosting: Why They Cannot Be Planned Separately
How BiggerBluButton Separates Live Session Load from Recording Storage
What BigBlueButton Recording Storage Looks Like on BiggerBluButton Plans
Recording Format Storage Comparison: Presentation vs Video vs Podcast vs MP4
Format Typical Size (1hr) What It Contains Best Use Case Presentation 150–400 MB Slides + whiteboard + audio + chat + polls Lectures, seminars, webinars — the most storage-efficient option Video 500 MB–2 GB All webcam streams + screen share + audio Virtual labs, performance sessions — largest footprint Podcast 30–80 MB Audio only — all participant voices Discussions, language learning, audio review — smallest footprint MP4 Download 300 MB–1.5 GB Exported video file — offline compatible Student download, external platform sharing, archiving Raw (temp) 2–5× final size Unprocessed event streams — deleted after processing Must be provisioned as temporary disk — self-hosted only concern Format Selection Impact on Storage Cost
Configuration Per Session (avg) Per Week (50 sessions) Per Semester (16wks) Presentation only ~275 MB ~13.5 GB ~216 GB Presentation + Podcast ~325 MB ~16 GB ~256 GB All 3 formats ~900 MB ~44 GB ~700 GB All 3 + MP4 download ~1.6 GB ~80 GB ~1.25 TB BiggerBluButton Storage Plans: From 100 GB to 30 TB — Which Plan Fits Your Institution?
Plan Price/mo Storage Max Users Concurrent Est. Recording Capacity (Presentation) Free $0 1 GB 50 1 ~3–6 hours total — pilot / demo use only Personal $7.99 100 GB 100 1 ~250–650 hours — solo tutor, small training use Bronze $39.9 500 GB 150 10 ~1,250–3,300 hours — small school, department pilot Silver $54.99 750 GB 250 20 ~1,875–5,000 hours — growing school or training org Gold $59.99 1 TB 300 30 ~2,500–6,600 hours — medium institution, semester archive Platinum $149 2 TB 600 100 ~5,000–13,000 hours — large school, multi-dept university Premium $199 4 TB 800 200 ~10,000–26,000 hours — full university, multi-semester library Enterprise-1 $299 5 TB 1,200 300 ~12,500–33,000 hours — large university or training network Enterprise-2 $750 10 TB 2,500 500 ~25,000–65,000 hours — district, consortium, large enterprise Enterprise-3 Contact 30 TB 10,000 2,000 ~75,000+ hours — national platform, multi-institution Sizing Your BigBlueButton Recording Storage: A Practical Planning Framework
Step 1: Count Weekly Recorded Sessions
Step 2: Calculate Average Session Duration
Step 3: Choose Your Format Mix and Apply Size Factor
Format mix Avg GB per recorded hour Presentation only 0.25–0.40 GB/hr Presentation + Podcast 0.30–0.50 GB/hr Presentation + Video 0.80–1.5 GB/hr All formats + MP4 1.5–2.5 GB/hr Step 4: Calculate Semester Total and Choose a Plan
Recording Playback Speed and Download Performance: What Affects It and How BiggerBluButton Optimises It
Factors That Affect BigBlueButton Recording Playback Speed
Bandwidth and Latency Considerations
Recording Retention Policies: Compliance, FERPA, GDPR, and How to Implement Them
Common Retention Policy Frameworks for Educational Institutions
Institution Type Typical Retention Rationale University (lecture recordings) 1–2 semesters (4–8 months) Students need access during the active course; minimal value after exam period ends University (course archives) 2–5 years Retained for curriculum review, academic integrity, and student grade appeal processes K-12 (student session recordings) Academic year only (max 12 months) COPPA and state-level regulations often require deletion at end of academic year Corporate training 3–7 years Compliance training recordings may be required for regulatory audit evidence GDPR-regulated (EU) As short as operationally required Data minimisation principle requires deletion when purpose is fulfilled — indefinite retention is non-compliant Implementing Retention on BiggerBluButton
deleteRecordings endpoint — which accepts a recordID parameter and removes the recording and its associated files. Combine with getRecordings to list recordings older than your retention threshold and delete them programmatically. Full API reference: docs.biggerbluebutton.com/api/referenceBigBlueButton Recording Workflow: How to Record, Save, Download, and Manage Recordings
How to Record a BigBlueButton Meeting on BiggerBluButton
record=true in the create call.getRecordings endpoint to retrieve the recording URL and metadata, then pull the file programmatically. Set up a webhook or post-publish script to automate this process for every completed recording.Managing the Recording Archive
publishRecordings to control whether a recording is visible to students via the LTI Recordings tab — unpublished recordings are stored but not accessible to non-admins.updateRecordings to add metadata tags (meta_course, meta_instructor, meta_semester) that make programmatic retention management and archive searching significantly easier.deleteRecordings to permanently remove recordings that have reached their retention expiry — this frees storage allocation immediately and can be automated via a scheduled script that queries recording age from the metadata.Canvas BigBlueButton Recording: How Storage Affects LMS Access and Sync
Method 1: Automatic LTI Recording Sync to Canvas (Recommended)
Method 2: Sharing a Recording Link to Canvas Manually
Storage Failure Impact on Canvas Recording Access
Resources for BigBlueButton Recording Storage Planning
FAQ: BigBlueButton Recording Storage, Retention, Cost, and Speed
How much storage does a BigBlueButton recording use?
How do I access BigBlueButton recordings after a session on BiggerBluButton?
How do I download recordings from BigBlueButton as MP4?
What happens when my BiggerBluButton storage is full?
How do I share a BigBlueButton recording with students in Canvas?
How often are BigBlueButton recordings backed up on BiggerBluButton?
Can students record Canvas conferences in BigBlueButton?
What is the most cost-effective BiggerBluButton plan for an institution recording 50 sessions per week?
Never Lose a BigBlueButton Recording to a Full Disk Again
