How to organise a website's files

A website's file structure rarely gets planned on purpose. It grows one upload at a time — a logo here, a PDF there, a folder created for a page that later got renamed — until finding anything means scrolling through a long, unsorted list and guessing. None of this is inevitable. A small amount of structure, applied early and kept up, pays for itself many times over the life of a site.

Start from what public_html actually is

Everything inside public_html is reachable by a visitor at a URL that mirrors its folder path. A file at public_html/images/logo.png is reachable at yourdomain.com/images/logo.png. This is worth keeping in mind because it means your folder structure is not just an organisational nicety for you — it becomes part of your site's actual URLs, at least for anything not handled by an application with its own routing.

A structure that works for most sites

If you are building or maintaining a straightforward site rather than running a large application like WordPress — which manages its own structure — a small number of top-level folders covers most needs:

The exact names matter less than having some structure at all and sticking to it. A site with everything — HTML, images, PDFs and stylesheets — sitting loose at the top level is not broken, but it becomes steadily harder to work in as it grows, and it makes URLs longer and less predictable as new sections get added without a clear place to put them.

If you are running an application, respect its structure

Platforms such as WordPress, and most other content management systems, come with their own folder conventions and expect specific things to live in specific places — themes, plugins, uploads and core files each have a defined location. Do not restructure these folders to match your own preferences; the application relies on the layout it was built with, and moving things around inside it is a common way to break updates and functionality that otherwise work automatically. Keep any custom, non-application content in a clearly separate folder instead of mixing it into the application's own structure.

Naming files consistently

A few small habits make a real difference once a site has more than a handful of files:

• Use lowercase, with hyphens instead of spaces. summer-sale-banner.jpg is safer across different servers and operating systems than Summer Sale Banner.jpg, and avoids the case-sensitivity trap where a link written as Logo.png fails to find a file actually named logo.png.
• Avoid special characters. Spaces, ampersands, and punctuation beyond hyphens and underscores can cause problems in URLs and in some tools that were not designed to handle them.
• Be specific rather than generic. homepage-hero-2026.jpg tells you far more six months later than image1.jpg does, particularly once a folder has accumulated dozens of similarly generic names.
• Date-stamp anything that will be replaced periodically. Reports, price lists, or seasonal graphics are easier to manage with a date in the file name than by relying on modification dates alone, which change every time a file is touched for any reason.

Keeping it tidy as the site grows

Structure decays gradually rather than all at once, so it is worth a periodic check rather than a one-off effort. A few minutes every few months looking through public_html for files that no longer belong, duplicates from testing, or a folder that has quietly become a dumping ground is usually enough to keep things manageable, especially compared with the time a proper clean-up takes once things have been left for years.

Hidden files still count

Configuration files such as .htaccess are part of your file structure even though they do not show in a default listing. Know where they are and what they do before restructuring folders around them, since moving or renaming a file that a hidden configuration file specifically refers to can silently break rules that depend on that exact path. See what hidden files are and how to see them if you have not looked at these before.

When you cannot find something

Even a reasonably organised site eventually has a file nobody can immediately place. Rather than guessing, use your file manager's search feature or connect over FTP and check by date modified — finding a file on your hosting account covers both approaches in more detail. And if you are just getting started and are not yet sure what belongs where at all, what public_html is is worth reading first.