Organising a website media library: naming, folders and cleanup

Open the uploads folder of a three-year-old business website and you will usually find the same scene: hundreds of files called IMG_20240712_113045.jpg, WhatsApp Image 2023-11-02 at 4.15.22 PM.jpeg, banner-final.jpg, banner-final-2.jpg and banner-final-USE-THIS.jpg. Nobody can tell what any of them show without opening each one. A tidy website media library is mostly about two habits: naming files before they go up, and clearing out what nothing uses any more.

Neither habit is glamorous, but they save hours of searching and keep your storage bill and backup times under control.

Name the file before you upload it

Renaming after upload is painful, because the file's address is already in use on pages and the change can break them. Do it on your computer first, as the last step before uploading.

A workable pattern is what-it-is, which-one, variant, all lowercase, words separated by hyphens rather than spaces or underscores. Some examples:

• product-steel-water-bottle-750ml-front.jpg
• team-anita-sharma-portrait.jpg
• banner-diwali-offer-2026-home.jpg
• store-interior-pune-shop-wide.jpg
• invoice-format-sample.pdf

Avoid spaces, because they turn into %20 in URLs and make links harder to read and share. Avoid capital letters, since some servers treat Photo.JPG and photo.jpg as different files and others do not, which causes broken images after a migration. Keep names reasonably short and skip words like final, new, latest and copy, which stop meaning anything after the second version.

A sensible file name also becomes part of the image URL, which gives search engines a small, honest clue about what the picture shows. It is not a ranking trick; it is the same clarity that helps your own team.

Folders, dates or tags: pick a structure you will maintain

Different platforms organise media differently, and the best structure is the one your system supports natively rather than one you fight against.

Date-based folders

Many systems file uploads by year and month automatically. This is fine for blog images and news photos where time is a reasonable way to find things. It is poor for product photos, which you look for by product, not by upload date.

Purpose-based folders

If your admin lets you create folders, a shallow structure works better than a deep one. Something like products, banners, team, blog, documents and logos is enough. Two levels deep is usually the limit before people stop filing correctly.

Tags or categories

Tags beat folders when one image belongs in several places, such as a store photo used on the about page and in a blog post. If your system supports tags, agree a small controlled list and write it down; free-form tagging drifts into ten spellings of the same word.

Whatever you choose, record the rule in a short document beside your other website notes, so a new joiner or agency follows the same pattern instead of inventing their own.

Upload discipline: size, format and duplicates

Most libraries balloon because of what goes in, not what stays. A few rules at the point of upload prevent a lot of later cleanup.

• Resize before uploading. A photo straight from a phone camera can be 4,000 pixels wide and several megabytes. Very few website slots need more than about 1,600 pixels across.
• Choose the right format. JPEG for photographs, PNG where you need transparency, SVG for logos and simple icons, and WebP where your platform supports it for smaller files at similar quality.
• Check before re-uploading. Search the library for an existing copy first. Many systems will happily store the same picture five times under slightly different names.
• Write alt text at upload time. It takes ten seconds while the image is fresh in your mind and is far harder to reconstruct later.
• Keep originals elsewhere. Store full-resolution masters in your own cloud drive or drive backup, not in the website library.

A cleanup routine that will not break pages

Deleting media is riskier than deleting a page, because an image can be used in places you forget: an old post, an email template, a PDF, a social listing that hotlinks to it. Work through it carefully once or twice a year.

1. Take a full backup of the site and the uploads directory before you touch anything.
2. Identify candidates: files not attached to any page or post, expired campaign banners, and obvious duplicates.
3. Search the site for each file name before deleting, including inside page content and theme settings.
4. Move candidates to a separate folder or an archive rather than deleting immediately.
5. Wait a few weeks, then check the server error log for missing-file entries, which usually appear as 404 responses for those paths.
6. Delete for real if nothing has complained, and note what you removed and when.

Be cautious with automated cleanup plugins. They judge "unused" by whether a file is attached in the database, which misses images referenced inside page-builder content, custom fields or hard-coded templates.

Watching storage growth before it becomes a bill

Check your uploads folder size every few months; most hosting control panels show it under disk usage. Sudden growth usually has one of three causes: a plugin generating many resized copies of every image, video files being hosted on the site instead of a video platform, or a bulk product import bringing in oversized photos.

Storage also affects backups. A library that has grown to several gigabytes makes backups slower and restores longer, which matters most on the day you actually need one.

Where to start on your own library

Do not try to fix everything. Start by writing your naming rule and applying it to new uploads from today. Then do one pass on the files that cause the most confusion, usually banners and product photos. Older blog images can stay as they are; the cost of renaming them exceeds the benefit.

If your media library has grown past what you can manage, or your admin has no folders, search or bulk tools at all, our team can help clean it up or improve the admin; see our website development services or raise a support request.

Frequently asked questions

Can I rename an image that is already used on my website?

You can, but the old URL stops working, so every page using it must be updated, and any external link to that image breaks. Re-uploading under a better name and switching the page over is usually safer.

How big should images on a business website be?

As a rough guide, keep most page images under about 200 KB and full-width banners under about 400 KB after compression. Check the result on a phone connection rather than office Wi-Fi.

Should I store videos in my website media library?

Generally no. Video files are large, strain your hosting and stream poorly from a basic server. Host them on a video platform and embed them instead.

Do file names affect image search results?

They are one small signal among several, alongside alt text, surrounding content and page context. Descriptive names help, but they will not make up for an otherwise weak page.