Understanding and Planning Your Moodle Storage Needs in 2026
Moodle storage planning fails when teams size the platform by user count alone. A 2,000-user text-based training site can stay small for years. A 150-user media program can fill storage in one term if learners upload video, audio, images, and assignment evidence directly into Moodle.
This guide was re-audited in May 2026 to remove unsupported infrastructure claims and keep the advice focused on what Moodle actually stores, how storage grows, and which decisions reduce risk.
What Counts Toward Moodle Storage
A Moodle site has three broad storage areas:
| Area | What it stores | Growth pattern |
|---|---|---|
| Moodle code | Core Moodle files, plugins, themes, local customizations | Changes during upgrades and plugin work |
| Database | Users, enrolments, grades, quiz attempts, logs, settings, metadata | Grows with activity and retention |
moodledata | Course files, submissions, generated files, backups, caches, temporary files | Usually the largest and fastest-growing area |
Moodle's file API stores files under moodledata/filedir by content hash. This means duplicate file content can be stored once even when referenced in multiple places, but it also means administrators should not manage production files by browsing directories manually. Use Moodle tools, reports, backups, and storage policies instead.
The 5-Step Moodle Storage Estimate
Use this formula when planning a new site or reviewing an existing one:
Required storage =
baseline platform storage
+ course material storage
+ learner submission storage
+ backup and restore working space
+ growth and safety bufferStep 1: Start With Baseline Platform Storage
For a small to medium Moodle site, reserve baseline space for:
- Moodle code, plugins, and themes.
- Database files or managed database exports.
- Caches, temp directories, logs, and upgrade working files.
- Operating system and monitoring overhead if self-hosted.
A practical baseline is 5-15 GB before user content. Very small SaaS plans can start lower, but they leave little room for backups, imports, and growth.
Step 2: Estimate Course Materials
Course authoring behavior matters more than course count.
| Course profile | Typical storage per course | Examples |
|---|---|---|
| Text-heavy | 100 MB to 5 GB | Pages, books, quizzes, forums, small PDFs |
| Document-heavy | 1-5 GB | Slides, PDF packs, worksheets, handouts |
| Mixed media | 5-15 GB | Images, audio, screen recordings, H5P, SCORM |
| Video-heavy | 20 GB or more | Recorded lectures, student media, simulation evidence |
If teachers upload full lecture videos directly into Moodle, storage and bandwidth become the bottleneck. Host video on a video platform or repository when possible, then embed or link it from Moodle.
Step 3: Estimate Learner Submissions
Submissions can quietly dominate storage because they multiply by user count.
| Submission pattern | Planning estimate per active learner per term |
|---|---|
| Quiz and forum only | 5-20 MB |
| Documents and PDFs | 25-100 MB |
| Images and audio | 100-500 MB |
| Video, portfolios, clinical evidence, design files | 500 MB to several GB |
Do not average across the whole institution if one program is media-heavy. Size for the largest content pattern, or isolate those courses with stricter upload rules and external media workflows.
Step 4: Add Backups And Restore Working Space
Backups are storage too. A healthy backup policy usually needs:
- Local temporary space while course or site backups are being created.
- Off-site backup storage.
- Restore working space for test restores and emergency recovery.
- Retention space for daily, weekly, and monthly restore points.
If your active Moodle footprint is 300 GB, a backup policy can easily require another 300 GB to several TB depending on retention. See The Ultimate Moodle Backup Policy for 2026 before assuming active storage and backup storage are the same thing.
Step 5: Add Growth And Safety Buffer
Add at least 30 percent headroom for normal growth and operational bursts. Add more if:
- You import old courses.
- You run term-end course backups.
- You allow large assignment uploads.
- You use the recycle bin heavily.
- You host video or SCORM packages directly in Moodle.
- You are close to exam, compliance, or certification windows.
Running out of storage during a term can break uploads, backups, sessions, cron tasks, or course editing. Plan upgrades before you hit the hard limit.
Storage Benchmarks By Site Type
These are planning ranges, not promises:
| Site type | Typical active storage | Watch closely when |
|---|---|---|
| Solo trainer or pilot | 1-20 GB | Courses include video or many PDFs |
| Small school or department | 20-200 GB | Learners submit documents or media |
| Mid-size institution | 200 GB to 2 TB | Courses are retained for multiple terms |
| Media-heavy or enterprise site | 2 TB or more | Video, portfolios, simulations, or long retention are required |
The right number depends on content policy. A 500-user site with video submissions can need more storage than a 5,000-user compliance training site.
The Biggest Storage Risks
Direct Video Uploads
Video is the fastest way to outgrow a Moodle plan. A single long HD recording can be hundreds of MB or several GB, and learners may upload multiple versions before they submit the final file.
Use YouTube, Vimeo, Panopto, Kaltura, institutional media servers, or another video platform when the content needs streaming, captions, privacy controls, adaptive playback, or analytics.
Course Backup Retention
Automated course backups are useful, but they can consume large amounts of storage if every course keeps many historical copies. Store backups off-site when possible and set retention deliberately.
Recycle Bin And Temp Directories
Deleted activities and courses can remain in recycle-bin storage for a configured period. Failed or interrupted backups can also leave large temporary files. Review trashdir, backup temp directories, and scheduled cleanup tasks as part of regular maintenance.
Unbounded Assignment Uploads
Large maximum upload sizes are easy for teachers to set and hard for administrators to fund. Use assignment-level limits, file type guidance, and media submission instructions.
Object Storage Can Help, But It Is Not A Shortcut
For larger Moodle installations, object storage can be part of the architecture. The ObjectFS plugin maintained by Catalyst IT is a known Moodle plugin for moving file storage to compatible remote object storage while Moodle continues to use its file API.
Object storage can improve scalability and cost control, but it requires careful design:
- Confirm compatibility with your Moodle version and hosting environment.
- Test backup and restore behavior.
- Understand local cache behavior.
- Monitor latency and failed transfers.
- Document how disaster recovery works when files are remote.
Do not install object storage just because storage is growing. First fix video policy, backup retention, upload limits, and stale course cleanup.
For a deeper optimization view, read Optimising Storage in Moodle.
How MoodleCloud And MooDIY Differ In Public Storage Positioning
MoodleCloud's public support documentation says plan storage quotas range from 5 GB to 50 GB, and that the way to get additional on-site storage is to upgrade to a larger plan. Its current public plan page lists 5 GB on Starter, 2.5 GB on Mini, 5 GB on Small, 20 GB on Medium, and 50 GB on Standard.
MooDIY's current hosting page lists a 50-user free base plan with 5 GB storage, then paid Essentials scaling in 100-user and 20 GB increments. It also says users are reminded at 90 percent of usage limits and may be unable to create users or upload files once limits are exhausted.
The practical planning advice is the same for both:
- Know the storage quota before you upload production content.
- Track usage monthly.
- Treat 80-90 percent utilization as an upgrade planning threshold.
- Do not wait until uploads fail.
- Ask support how full-site backup downloads and exports affect quota and temporary storage.
For MooDIY-specific storage positioning, also see Oodles of Storage Space at MooDIY.
Storage Policy Checklist
Use this checklist before a new term or migration:
- Set maximum upload size defaults.
- Define which media must be hosted outside Moodle.
- Review course backup retention.
- Test cleanup tasks for temp and recycle-bin data.
- Monitor top courses by storage usage.
- Review backup and restore working space.
- Plan storage upgrade triggers at 80 percent and 90 percent.
- Document who approves large imports, course clones, and video-heavy activities.
- Confirm whether custom repositories or object storage are supported by your hosting plan.
Conclusion
Storage planning is not a one-time number. It is a policy. Estimate by content type, enforce upload rules, keep video out of Moodle where possible, size backups honestly, and monitor growth before the platform reaches its limit.
If you are choosing a host, compare both the headline quota and the operational behavior around backups, exports, support, and upgrades. The cheapest storage plan is not cheap if it fails during a submission deadline.