What is a WordPress theme, technically speaking
Inside /wp-content/themes/ every folder is a theme candidate. WordPress recognizes a folder as a valid theme when it contains a style.css file with a specific comment header at the top listing the theme name, author, version, and description. Without that header, WordPress will not list the theme under Appearance → Themes at all.
Beyond style.css, a classic theme typically ships index.php as a fallback template, header.php and footer.php for shared chrome, functions.php for setup code and hooks, and a screenshot.png (ideally 1200x900) shown in the theme picker. Newer block themes replace most of that PHP with HTML template files and a theme.json configuration file instead.
What a theme actually controls
A theme governs typography, color palettes, spacing, header and footer structure, how blog archives and single posts are arranged, and which widget areas or block patterns are available. It also decides how images, menus, and forms are styled through CSS enqueued via wp_enqueue_style.
A theme does not store your posts, pages, comments, or media — those live in the WordPress database and uploads folder regardless of which theme is active. That is why you can switch themes without losing content, though custom layouts built with page-builder shortcodes can sometimes look broken until you adjust them.
- Controls: layout, typography, colors, header/footer, template hierarchy
- Does not control: your actual posts, pages, database content, or installed plugins
- Lives in: /wp-content/themes/your-theme-name/
The template hierarchy in one page
WordPress decides which template file to load using a fixed lookup order called the template hierarchy. For a single blog post it checks single-{post-type}-{slug}.php, then single-{post-type}.php, then single.php, and finally falls back to index.php if nothing more specific exists.
The same pattern repeats for categories, tags, archives, and pages: WordPress always looks for the most specific file first and walks down to the generic fallback. Understanding this hierarchy is the single most useful thing you can learn if you ever plan to customize a theme, because it tells you exactly which file to edit.
Classic themes vs block themes
A classic theme uses PHP template files and the Customizer for options; edits to structure usually require code or a page builder plugin. A block theme, enabled by Full Site Editing since WordPress 5.9, uses HTML template files built from blocks plus a theme.json file that defines colors, spacing, and typography as structured settings rather than CSS.
Block themes let you edit headers, footers, and templates directly in the Site Editor without touching PHP. Classic themes remain extremely common because of their maturity, the size of the classic plugin ecosystem, and the fact that many businesses simply need a stable, predictable layout rather than a fully editable design system.
Where themes come from
You can install a theme from the official WordPress.org repository (free, reviewed for security), from a commercial theme shop, from a custom build by a developer, or by uploading a .zip file yourself under Appearance → Themes → Add New → Upload Theme. Uploaded zips are limited by your host's upload_max_filesize in php.ini, so very large theme packages sometimes need that value raised.
If you already have a design you like — a live site, a Figma export, or a page you built elsewhere — tools like Themify can package that exact design into a valid theme.zip with the correct style.css header and file structure, which is faster than hand-building the boilerplate from scratch.
Themes vs plugins, briefly
It is worth stating clearly: themes handle appearance, plugins handle functionality. A contact form, an SEO toolkit, or an ecommerce cart is a plugin's job, not a theme's, even though badly built themes sometimes blur that line by bundling shortcodes and widgets that behave like plugin features.
How to choose a theme
Start from what the site needs structurally — blog, portfolio, store, documentation — rather than picking on looks alone, since most themes can be restyled with CSS but rarely restructured cheaply. Check the theme's last update date and support forum activity on WordPress.org before installing anything free.
- Define your site's content types (posts, products, portfolio items)
- Shortlist 2-3 themes that match that structure, not just the color scheme
- Check update history, ratings, and support responsiveness
- Install on a staging site first and test with your real content
- Activate on production only after checking mobile layout and page speed
Frequently asked questions
- Can a WordPress site work without a theme?
- No, WordPress always requires an active theme to render pages; if none is installed, WordPress falls back to a default theme it ships with, such as Twenty Twenty-Four.
- Will changing my theme delete my content?
- No, your posts, pages, and media stay in the database and uploads folder. What can break is custom styling or shortcodes tied to the old theme, so always preview a new theme before fully switching.
- What is the difference between a theme and a child theme?
- A child theme inherits everything from a parent theme but lets you override specific files or styles safely, so your customizations survive when the parent theme updates.
- Do I need coding knowledge to use a WordPress theme?
- No, most themes are usable out of the box through the Customizer or Site Editor. Coding knowledge only becomes necessary for deep structural changes beyond what the theme's built-in settings expose.
- How many themes can I have installed at once?
- You can install as many themes as you want, but only one can be active at a time. Inactive themes just sit in wp-content/themes without affecting the live site.