A theme preview can look perfect while your real site has a different menu, twice as many widgets, and an awkward old shortcode in the footer. Installing the files is the easy part. The careful part is changing presentation without surprising readers—or discovering too late that your customization lived inside the theme you just replaced.

What changes when a theme changes

A WordPress theme is a collection of templates, styles, images, and code that controls how stored content is presented. Activating another theme does not normally delete posts, pages, or media, but it can change menus, widget areas, template assignments, block styling, and features supplied by the previous theme.

Only one theme is active at a time. Other installed themes remain on disk and can receive updates, but they do not control the public design. That distinction makes it possible to install and inspect a candidate before committing to it.

Take a recoverable snapshot first

  • Create a complete backup that includes both the database and wp-content files.

  • Confirm where the backup is stored and how restoration works.

  • Capture the current menus, widget areas, homepage setting, and any theme-specific options.

  • Use a staging copy for a business or high-traffic site rather than experimenting in production.

  • Update WordPress and resolve existing errors before blaming them on a new theme.

Method 1: install from the WordPress Theme Directory

In the administration area, open Appearance → Themes, select Add New, and search by theme name, author, keyword, or feature. Open the details and preview rather than choosing from a thumbnail alone. Consider whether the theme is maintained, compatible with your WordPress version, documented, accessible, and suitable for the content you already have.

  1. Select Install to download the theme to your site.

  2. Wait for WordPress to report that installation completed.

  3. Choose Live Preview and inspect the homepage, a long post, an archive, search, and a 404 page.

  4. Return to Appearance → Themes and activate only after the preview is credible.

The official Appearance Themes screen documentation describes the directory installer as the easiest route for themes published in the WordPress.org directory.

Method 2: upload a theme ZIP through the dashboard

Use this route for a theme supplied as an installable ZIP by its author or vendor. Verify the source and keep the original download and license information. A “full package” from a vendor may contain documentation, plugins, and another ZIP; WordPress expects the installable theme archive itself.

  1. Open Appearance → Themes → Add New.

  2. Select Upload Theme.

  3. Choose the installable .zip archive and select Install Now.

  4. Read the result screen; do not treat a partial or failed upload as success.

  5. Preview the installed theme before activation.

Method 3: install through SFTP or the hosting file manager

Manual installation is useful when the dashboard upload limit is too small or the administration installer cannot write to the theme directory. Extract the trusted archive locally or with the hosting file manager, then place the theme’s single directory under wp-content/themes/.

Expected theme directory layouttext
wp-content/
└── themes/
    └── example-theme/
        ├── style.css
        ├── functions.php
        └── templates/

Exact files vary, but the theme directory must not be accidentally nested inside another copy of itself.

Reading the directory layout

  • example-theme is the directory WordPress discovers beneath wp-content/themes.

  • style.css contains required theme metadata in classic and block themes; a missing valid stylesheet can trigger the “stylesheet is missing” message.

  • functions.php is executable PHP when present, which is why a theme archive must come from a source you trust.

  • A path such as example-theme/example-theme/style.css indicates an extra nesting layer and may keep WordPress from recognizing the theme.

After the transfer finishes, return to Appearance → Themes. WordPress should list the theme without requiring a database import. If it does not, inspect the folder structure and the dashboard’s broken-theme message rather than changing broad file permissions.

Preview with the awkward pages, not only the homepage

  • A post with a wide image, table, code block, and several heading levels.

  • Navigation with dropdowns, plus keyboard focus and mobile-menu behavior.

  • Category, tag, search-result, author, and 404 templates.

  • Comments, forms, ecommerce flows, or membership screens the site relies on.

  • Header logo dimensions, footer content, sidebar widgets, and featured images.

  • Light and dark preferences if either the theme or site supports them.

WordPress’s current theme documentation explicitly warns against activating a theme when its preview is blank. A blank preview is evidence to investigate, not an invitation to test on visitors.

Activate, then perform a short production check

  1. Activate the theme from Appearance → Themes.

  2. Open the public site in a private browser window so an administrator toolbar does not hide layout problems.

  3. Test the primary navigation, homepage, representative posts, search, and forms.

  4. Check the browser console and server error log if the page is incomplete or returns an error.

  5. Review menus, widgets, the Site Editor or Customizer, and homepage assignment.

  6. Purge only the caches used by your host or caching plugin, then check again on mobile.

Use a child theme when customization belongs in code

Editing a third-party parent theme directly makes future updates dangerous because updated files can overwrite those changes. A child theme provides its own files while inheriting from the parent, allowing the parent to receive maintenance and security updates.

Not every visual change needs a child theme: block-theme style settings, supported custom CSS, and a small site-specific plugin may be better homes depending on the change. The rule is simpler than the tooling: do not bury business-critical behavior in a vendor file you plan to overwrite.

Failures that look worse than they are

“The package could not be installed. The theme is missing style.css”

Confirm that you uploaded the installable theme ZIP rather than a larger download bundle. If manually installed, inspect for an extra nested directory and verify that the archive is actually a WordPress theme, not a plugin or unrelated template.

The upload exceeds the server limit

Use the hosting file manager or SFTP, or ask the provider about the account’s upload limits. Avoid installing an unknown “limit remover” merely to upload another package.

The site shows a critical error after activation

Use WordPress Recovery Mode if its email arrives. Otherwise rename the new theme directory through SFTP or the host’s file manager so WordPress can fall back to an available default theme. Then inspect the error log and compatibility requirements before trying again.

The design works, but menus and widgets moved

Assign menus to the new theme’s menu locations and rebuild content in its available widget areas. The data may still exist even when the new theme has no equivalent display location.

A theme is a maintained dependency, not a coat of paint

The satisfying moment is not the first pretty homepage. It is the point where real content still works, updates remain possible, and you know how to reverse the change. That is what turns theme installation from a hopeful click into a controlled release.

Continue shaping the site