Start with the tasks people need to do
A media library is useful when an editor can find the right file, tell whether it is still needed and use it without guessing. Before reorganizing anything, look at the tasks your team repeats: replacing a staff photo, updating a downloadable form, finding an image for a service page or checking whether a document is out of date. Those tasks should shape your system.
List the kinds of files you keep and who uploads them. A small site may need only a few broad groups, such as people, services, events and documents. Note where the CMS already offers search, tags, captions or folders. You do not need to use every feature; choose the smallest set that helps editors answer practical questions.
Give files names that make sense out of context
A useful file name describes the subject or purpose before anyone opens the file. Use short, ordinary words in a consistent order, separated by hyphens or underscores. For example, community-garden-volunteers.jpg is more informative than IMG_4821.jpg. For documents with recurring editions, add a meaningful version label, such as volunteer-guide-2025.pdf, if the year helps editors distinguish copies. Avoid labels such as final or new, which quickly lose their meaning.
Keep names specific without packing them with keywords. Two photos of the same subject may need a distinguishing detail, such as community-garden-volunteers-planting.jpg and community-garden-volunteers-group.jpg. Decide how your team will handle capitalization, spaces and special characters, then write down the rule. Consistency makes files easier to scan and can prevent awkward links when file names appear in URLs.
File names are not a substitute for accessible text on a page. An image’s alternative text should reflect what the image communicates in that particular context. A decorative image may need no descriptive alternative text, while an informative image may need a description that differs from its file name. Captions and credits, when needed, also serve different purposes.
Build a folder structure you can remember
If your CMS supports folders, start with a shallow structure based on how editors look for files. A small organization might use People, Programs, Places and Documents rather than a separate folder for every page. Within Documents, a second level for Forms and Guides may be helpful. Deeply nested folders tend to create a new problem: editors must remember a file’s exact location before they can find it.
Choose one primary home for each file. If a photo appears on several pages, store it once and reuse it where the CMS allows. Tags or searchable descriptions can capture other ways to find it without making duplicate copies. If your CMS has no folders, the same naming rules and metadata can still provide order. Test your proposed structure by asking someone else to find a few common files; revise any category that makes them hesitate.
Clean up carefully, then set an upload routine
For an existing library, begin with a manageable group rather than renaming everything at once. Look for unclear names, duplicates and documents that may be outdated. Before deleting or replacing a file, check whether pages link to it or embed it. Some CMS platforms change a file’s URL when it is renamed or moved; others keep the original address. If you are unsure, test with a low-risk file first and check the affected pages afterward.
Create a short upload checklist for editors: choose the right file, give it a clear name, place it in the right folder, complete useful metadata and preview it on the page. Check whether the image needs alternative text or a caption in its specific use. For downloadable documents, give the visible link text a meaningful label so visitors know what they will open. Keep private or sensitive files out of the public media library unless you have confirmed the access controls meet your needs.
Keep the system small enough to maintain
A good organizing scheme should survive a busy week and a new team member. Keep the rules in a short shared guide with a few examples, including one for an image and one for a document. Make clear who can add new top-level folders or change naming conventions. That small decision can prevent several near-identical categories from appearing over time.
Review the library during ordinary content maintenance. When you update a page, check whether its files are still accurate, properly described and easy to identify. Set aside questionable files for review rather than deleting them on sight. The goal is not a perfectly tidy archive; it is a reliable working library where people can find, use and maintain the right media with less effort.
