Automatic Date-Based Folder Structure for Media Uploads

[sizouh]

The Problem

Currently, when uploading images through the Media Manager in Joomla, files are stored directly inside the default /images directory (or manually selected folders).

Over time, especially on active websites (news portals, blogs, e-commerce, etc.), the /images folder can become extremely crowded with thousands of files. This creates several issues:

Difficult file management and navigation

Slower browsing inside Media Manager

Harder server-level maintenance and backups

Poor organizational structure

There is no built-in automatic date-based folder organization system.

Proposed Solution

Introduce an optional feature in Joomla Media Manager that automatically organizes uploaded files into date-based folders.

For example:

When an image is uploaded, Joomla automatically creates a folder structure like:

/images/2026/02/24/

The file is then stored inside the corresponding daily folder.

This feature could:

Be optional (enabled/disabled from Global Configuration → Media settings)

Allow choosing the structure format:

Year/Month

Year/Month/Day

Custom format (YYYY/MM/DD etc.)

Be implemented in a way that remains backward compatible

Why This is Useful

Better scalability:
Large and content-heavy websites will remain organized even after years of operation.

Improved performance and usability:
Browsing the Media Manager becomes faster and more structured.

Standard practice in modern CMS platforms:
Many modern content management systems organize uploads by date by default.

Cleaner server structure:
Makes maintenance, migrations, backups, and CDN integrations easier.

Core integration advantage:
Currently, this can only be solved via custom development or extensions. Having it in Joomla core ensures consistency, reliability, and extensibility for developers.

[brianteeman]

How does this improve usability? If I want to re-use an image how can I find it. I would have to check every single folder

How does this improve performance? Please dont just state something as a fact without backing it up.

As you correctly point out there are extensions freely available that will provide this. How will having it in the core make any difference to reliability and extensibility for developers?

[sizouh]

Thank you for the thoughtful questions. Let me clarify and provide more concrete reasoning.
How does this improve usability?
The intention is not to replace manual organization, but to improve structure for high-volume websites.
On content-heavy websites (news portals, magazines, e-commerce), thousands of files accumulate in a single directory over time. Browsing a directory containing 5,000–20,000 files becomes difficult both in Media Manager and at the server level.
Date-based organization helps in several practical scenarios:
Editors usually upload images close to the publishing date of an article.
If they need to reuse a recent image, they can navigate directly to the relevant month/year folder.
Server administrators can locate assets faster when reviewing logs, backups, or file changes.
FTP and hosting file managers perform significantly better when directories are not overloaded with files.
For reuse scenarios:
This feature should be optional. Websites that rely heavily on reusing a central media library can keep the current flat structure. The goal is to offer flexibility for large-scale publishing environments.

How does this improve performance?
You're right to ask for clarification.
The performance improvement is not primarily about frontend rendering. It concerns:
File system lookup efficiency:
Many file systems (especially on shared hosting) experience slower directory scanning when thousands of files exist in a single folder.
Media Manager responsiveness:
Listing very large directories requires more processing and memory compared to smaller segmented folders.
Backup and sync operations:
Tools that scan file systems (backup, deployment, rsync, etc.) perform more efficiently when directories are structured rather than flat.
This is a scalability improvement rather than a raw performance boost.
Why core instead of extensions?
While extensions exist, core integration offers:
Consistent implementation across installations
Long-term maintenance with Joomla updates
Standardized API behavior for developers
Better integration with Media Manager permissions and workflows
If implemented in core as an optional configuration, it:
Avoids fragmentation of different upload-structure extensions
Provides a predictable file structure developers can rely on
Keeps the feature extensible via events or configuration overrides
This would not replace extensions, but provide a standardized baseline for structured media storage.

To be clear:
This should be optional.
It targets high-volume publishing environments.
It is a scalability and maintainability improvement rather than a universal usability change.

I appreciate the discussion and am happy to refine the proposal further.

[brianteeman]

You talk about high volume sites and shared hosting - thats an oxymoron ie the two things cant exist together

The reality is that chosing to create sub-directories by date adds nothing (unless you want to clone another cms) to help with structured storage. just creating random folders with no meaning wont help your site with thousands of images if they want to find and reuse an image. nor would it have any impact on permissions

All your arguments for users not storing everything in one folder are reasonably valid (other than performance) but i dont see anything being improved by just stuffing everything into date folders. If that is what you want then there are extensions that will do that.

[HLeithner]

The Joomla Maintainer Team decided at the 04.03.2025 meeting to reject this feature. This is better handled by a custom plugin.