How to edit the footer in WordPress

The WordPress footer is one of the most-asked-about pieces of a site and one of the most confusing, because there is no single place to edit it. Where the footer lives depends entirely on what kind of theme you are running. A site on Twenty Twenty-Five uses a completely different editor than a site on an older classic theme, and a site built with Elementor uses a third path that ignores both of those. If you have ever opened Appearance and found nothing that says “Footer,” this is why.

This guide walks through every footer-editing path in WordPress – block themes, classic themes with the Customizer, classic themes without one, widget-based footers, page builder footers, and direct code edits in a child theme. It covers the safe ways to remove the “Powered by WordPress” text, how to add custom HTML like social links or copyright notices, and why editing footer.php in the parent theme is the one thing you should never do.

Short answer: which footer editor do I use?#

The first step is figuring out what kind of theme you are on. Go to Appearance in the WordPress admin and look at what is listed:

• If you see Editor (sometimes shown as “Site Editor”), you have a block theme. Edit the footer at Appearance > Editor > Patterns > Footer (or Appearance > Editor > Templates, depending on the theme).
• If you see Customize, you have a classic theme that uses the Customizer. Edit the footer at Appearance > Customize, then look for a Footer section, Widgets panel, or a Colors/Theme Options panel.
• If you see Widgets but no Customize or Editor, you have a classic theme without Customizer support. Edit the footer at Appearance > Widgets by placing content in the Footer widget areas.
• If you are running Elementor Pro, Divi, Beaver Builder, or another page builder with theme-building features, the footer is a template inside that builder – not in WordPress’s native screens.

Footer editor by theme type at a glance#

If you do not know which category your theme falls into, open Appearance > Themes and note the active theme name. The default WordPress themes released since 2022 (Twenty Twenty-Two, Twenty Twenty-Three, Twenty Twenty-Four, Twenty Twenty-Five) are all block themes. Older default themes like Twenty Twenty-One, Twenty Twenty, and Twenty Nineteen are classic themes. Third-party themes vary – check the theme description or documentation if you are unsure.

Editing the footer in a block theme#

Block themes, introduced with WordPress 5.9 in early 2022, replaced the old Customizer with the Site Editor. Instead of separate screens for headers, footers, menus, and widgets, the entire site is built from reusable block-based template parts that you edit visually.

Step-by-step: edit the footer in the Site Editor

1. Go to Appearance > Editor.
2. In the sidebar, click Patterns (on some themes this is under Template Parts).
3. Find the Footer pattern in the list and click it.
4. The footer opens in the block editor. You can now:
   • Click any block to edit its text or styling.
   • Use the + button to add new blocks (paragraph, social icons, navigation, image, columns).
   • Use the block toolbar to change alignment, typography, colors.
   • Drag blocks to reorder them.
5. Click Save in the top-right. A confirmation dialog shows what will be saved – usually just the Footer template part.

Because block theme footers are template parts, the edit applies site-wide instantly. Every page, post, archive, and single post that uses the footer part reflects the change on the next load.

Removing the “Proudly powered by WordPress” text in a block theme

Most block themes include a footer pattern with a small paragraph block that says “Proudly powered by WordPress” or similar. It is just a block. Click it, select all, delete it, or replace the text with your own copyright line like © 2026 Your Company. All rights reserved. . Save. The change is live.

Adding social links, a menu, or a copyright line

In the Site Editor, use the block inserter:

• Social Icons block – supports 30+ platforms (Twitter/X, Facebook, Instagram, LinkedIn, YouTube, Mastodon, GitHub). Add the block, then click each icon to add a URL.
• Navigation block – for a footer menu (privacy, terms, contact links). If you already have a menu configured, pick it from the dropdown; otherwise create a new one.
• Paragraph with inline HTML – for a copyright line. Use the current year with dynamic HTML if you want it to auto-update (see the Adding custom HTML section below).

Editing the footer template directly (not just the pattern)

Some block themes split the footer across a pattern and a template. If editing the Footer pattern does not change what you see on the site, the actual footer is probably in a template:

1. Appearance > Editor > Templates.
2. Open the template you are viewing – usually Index, Single, or Page.
3. Scroll to the bottom of the template – the footer template part will be embedded there.
4. Click the Footer template part to enter it, or click the three-dot menu and choose Edit.

From there, the same save-and-go-live flow applies.

Editing the footer in a classic theme with the Customizer#

If your theme shows Appearance > Customize, you are on a classic theme that supports the Customizer. The Customizer is WordPress’s older live-preview editor. Footer controls depend entirely on what the theme author chose to expose – some themes have a dedicated Footer panel, others bury footer settings under Widgets or Colors & Theme Options, and others offer nothing beyond the footer widget areas.

Step-by-step: find the footer in the Customizer

1. Go to Appearance > Customize.
2. Look for any of these panels (theme-dependent):
   • Footer or Footer Settings
   • Widgets – usually contains Footer 1, Footer 2, and so on
   • Colors – sometimes the footer background and text color live here
   • Theme Options or General Settings – some themes hide a footer copyright field here
3. Make changes, watch the preview on the right update live.
4. Click Publish at the top-left.

The footer widget areas

Classic themes typically define one to four footer widget areas – usually three or four columns at the bottom of every page. You fill them with widgets:

• Recent posts
• Custom HTML
• Navigation menu
• Image
• Contact info
• Text

Go to Appearance > Widgets or Appearance > Customize > Widgets and drag widgets into the Footer 1, Footer 2, Footer 3 slots. For a plain copyright line, use a Custom HTML or Paragraph widget.

Where the “Powered by WordPress” text hides in a classic theme

Most classic themes offer one of three options for the “Powered by” line:

• A Customizer field called Footer Credit, Footer Text, Copyright Text, or similar. Replace the default with your own text.
• A hardcoded line in footer.php that you cannot change from the admin. This is the case for many free themes. To change it, you need a child theme (see below).
• Hidden behind a premium/pro option that only activates with the paid version of the theme. Frustrating, but common. The workaround is either pay for the pro version, switch themes, or use CSS to hide the line (below).

Hiding the footer credit with CSS (last resort)

If the theme does not give you a way to edit the credit and you cannot modify footer.php , you can hide it with CSS. Inspect the element in your browser’s developer tools to get the selector (often .site-info , .footer-credit , .site-credits , or an element with copyright in the class name), then add:

.site-info {
    display: none;
}

to Appearance > Customize > Additional CSS. See how to edit and add custom CSS in WordPress for the full walkthrough on adding custom CSS safely.

Hiding the credit with CSS is not the same as removing it – the HTML is still there, just not visible. Most theme licenses allow this; some do not. Check your theme’s license before hiding credit links if you are on a premium theme.

Editing the footer in a classic theme without a Customizer option#

A small number of older classic themes do not register Customizer support at all. In that case:

1. Go to Appearance > Widgets.
2. Place widgets in the available Footer widget areas.
3. For anything beyond what the widget areas allow – changing the “Powered by” line, changing colors, changing layout – you need a child theme.

The widget-only approach is limited. For a modern site, the better long-term answer is to switch to a newer theme that supports either block editing or at least the Customizer. Older classic themes without Customizer support often also lack security updates and block editor compatibility, which becomes a bigger problem over time.

Editing the footer with a page builder (Elementor, Divi, Beaver Builder)#

If you are running a page builder with theme-building capability, the native WordPress footer editors do not apply – the page builder has replaced the theme’s footer with a template of its own.

Elementor Pro

1. Go to Templates > Theme Builder (Elementor Pro only – free Elementor cannot build theme parts).
2. Click Footer in the sidebar.
3. Click Add New Footer, or edit the existing one.
4. Build the footer with Elementor widgets (heading, text, social icons, nav menu, columns).
5. Set Display Conditions – usually Entire Site.
6. Publish.

Elementor footers live as custom post types (elementor_library), separate from footer.php . To see which footer template is live on the front end, go to Templates > Theme Builder and look for the one marked Published under Footer.

Divi

1. Go to Divi > Theme Builder.
2. Find Default Website Template (or add a new template for specific pages).
3. Click Add Global Footer (or edit the existing one).
4. Build using Divi modules.
5. Save.

Beaver Builder Themer

Beaver Builder Themer uses a similar Theme Builder screen under Beaver Builder > Themer Layouts. Create or edit a Footer layout there.

Why page builder footers override everything else

When a page builder’s Theme Builder is active, WordPress’s normal footer rendering path (calling get_footer() and loading footer.php ) is either skipped entirely or wrapped by the builder’s logic. Editing footer.php , the block Site Editor, or the Customizer will not change the front-end footer while the builder’s footer template is published. This catches people out all the time – they edit in the wrong place and wonder why the footer is not changing. If you have Elementor Pro, Divi, or Beaver Themer active, the builder is the source of truth for the footer.

Adding custom HTML to the footer#

The most common footer customization after the basics: adding social links, legal links, an address, tracking scripts, or a dynamic copyright year.

Option 1: the Custom HTML block (block themes) or Custom HTML widget (classic themes)

This is the safe path. Both the block editor and the widget system include a Custom HTML option that accepts raw HTML. Use it for:

• Address blocks with microdata
• Privacy and terms links
• Simple copyright lines with dynamic year
• Small tracking snippets (though Google Analytics and similar are better handled by a dedicated plugin)

Example of a simple copyright line with the current year, using a small inline script:

<p>© <span id="copyright-year"></span> Your Company. All rights reserved.</p>
<script>document.getElementById('copyright-year').textContent = new Date().getFullYear();</script>

Paste that into a Custom HTML block in the Site Editor or a Custom HTML widget in the Widgets screen, save, and the year updates automatically every January 1.

Option 2: the Shortcode block or a PHP-powered shortcode

If inline JavaScript is not your preference, register a shortcode that outputs the current year on the server. Add this to your child theme’s functions.php :

function copyright_year_shortcode() {
    return date('Y');
}
add_shortcode('year', 'copyright_year_shortcode');

Then in the footer, use [year] in a paragraph or Custom HTML block, and WordPress will replace it with the current year at render time. This is cleaner than the JavaScript approach because the value is set server-side before the page is cached. Speaking of caching, any dynamic content in the footer needs to be cache-aware – if your site is behind a full page cache (most production WordPress sites are), a server-rendered date('Y') will be cached along with the rest of the page and updates only when the cache is cleared. See how to clear the WordPress cache, every layer explained for the details.

Option 3: a menu for legal and utility links

For privacy, terms, cookie policy, and contact links, a proper menu is better than a Custom HTML block. It gives you a single place to add, remove, or reorder links without editing markup every time. Create the menu at Appearance > Menus, or the Navigation block in the Site Editor, and place it in the footer. See how to add and manage menus in WordPress for the full walkthrough.

Editing footer.php in a child theme (advanced)#

Everything above is the answer for 95% of people. The remaining 5%: you need to change something in the footer that none of the admin-side editors expose. Maybe you are injecting structured data, adding a specific HTML wrapper around the footer for a tracking integration, or removing a link that the theme author hardcoded without a filter.

For that, you edit footer.php – but only in a child theme, never in the parent theme directly.

Why you must never edit the parent theme’s footer.php

If you edit wp-content/themes/parent-theme/footer.php directly, the very next time the parent theme updates, your changes are wiped out. Theme updates overwrite all files in the parent theme directory. It does not matter if you took careful notes, commented your changes, or committed them to git on the server – the next auto-update or manual update from Appearance > Themes > Update will destroy the edit.

The only safe pattern is a child theme, which is a separate, smaller theme that inherits everything from the parent but overrides specific files.

Creating a minimal child theme

A child theme needs just two files in a new directory under wp-content/themes/ :

wp-content/themes/your-theme-child/style.css :

/*
Theme Name: Your Theme Child
Template: your-theme
*/

Replace your-theme with the exact folder name of the parent theme (check wp-content/themes/ to see it).

wp-content/themes/your-theme-child/functions.php :

<?php
add_action('wp_enqueue_scripts', 'child_theme_enqueue_styles');
function child_theme_enqueue_styles() {
    wp_enqueue_style('parent-style', get_template_directory_uri() . '/style.css');
}

Activate the child theme at Appearance > Themes. All your existing customizations from the parent theme carry over because the child theme inherits the parent’s templates and settings.

To override the footer, copy footer.php from the parent theme directory into the child theme directory, then edit the copy. WordPress will load the child’s footer.php instead of the parent’s. Parent theme updates no longer touch your customization.

This pattern works for any template file – header.php , single.php , page.php , and so on. It is the canonical way to modify classic theme markup without losing your changes on the next update. For larger customizations – rebuilding big parts of the theme rather than tweaking – consider building a custom WordPress theme from scratch instead of fighting with a third-party theme’s footer markup.

Block themes and child themes

Block themes can also have child themes, but the setup is different and rarely necessary. Most block-theme customizations can be done entirely through the Site Editor and saved as “Global Styles” overrides in the database. You only need a block theme child if you want to override specific template files or block patterns. The official block theme handbook at developer.wordpress.org covers the details.

How long does footer editing take?#

If you are looking at an hour of poking around without progress, the most likely cause is that you are editing in the wrong place – usually because a page builder’s theme footer is overriding whatever you change in the native WordPress editors. Check Templates > Theme Builder in Elementor Pro, Divi > Theme Builder in Divi, or Beaver Builder > Themer Layouts first.

Common mistakes and how to avoid them#

• Editing footer.php in the parent theme and losing changes on update. Always use a child theme for file edits.
• Expecting the Customizer footer panel on a block theme. Block themes deliberately do not expose the Customizer. Use Appearance > Editor.
• Changing the footer in the Site Editor while a page builder has its own footer template published. The builder overrides the native footer. Edit the builder’s footer template instead.
• Using inline JavaScript for the copyright year without considering caching. Page caches serve the HTML as-is. JavaScript still runs in the browser and updates the year, but if you are using server-side date() without the shortcode approach, the cached page shows the wrong year for its entire TTL.
• Deleting the “Powered by WordPress” line and seeing an empty container. Some themes wrap the credit in a <div> that still takes up space. After removing the text, you may need to also hide the wrapper element with CSS, or edit the theme template part to remove the empty wrapper entirely.
• Adding a script tag with Google Analytics or Google Tag Manager through the footer. It works, but it puts the tag at the bottom of the page where it fires last. For tracking you usually want the tag in the <head> . Use a plugin like Insert Headers and Footers, or the head hook in a small site-specific plugin.
• Assuming the footer is theme-wide when it is actually template-specific. Some themes have different footers for pages, posts, and archives. If your change only shows up on some pages, look for multiple footer template parts.
• Hiding the theme author credit on a theme whose license requires it. Most commercial themes allow it. Some free themes (particularly GPL-licensed themes distributed through developers rather than the WordPress.org repository) have attribution-required licenses. Check before you hide.

Summary#

Where you edit the WordPress footer depends on your theme. Block themes use Appearance > Editor > Patterns > Footer. Classic themes use the Customizer or the Widgets screen. Page builders like Elementor Pro and Divi have their own Theme Builder sections that override everything else. For changes beyond what the admin screens expose, copy footer.php into a child theme and edit the copy – never touch the parent theme’s files directly.

For most sites, the right answer is the visual editor that matches the theme, the Custom HTML or Shortcode block for dynamic content like a current-year copyright, and a proper menu for legal and utility links. The child theme route only becomes necessary when a specific piece of footer markup has to change and the theme does not give you an option for it. Start with the admin-side tools, and reach for code only when nothing else works.

How Hostney handles footer editing#

Nothing about editing the WordPress footer is specific to the host – the work happens inside WordPress – but a few Hostney features make the process faster and safer.

For the footer.php edit path, you can use the built-in file manager to create the child theme directly in the browser, without setting up SFTP. The file manager’s code editor has syntax highlighting for PHP, CSS, and HTML, so creating style.css and functions.php for a child theme takes a minute. The chmod modal lets you set correct file permissions on the new directory, which matters because WordPress is strict about theme file permissions.

FastCGI page caching sits in front of every WordPress site on Hostney, which is relevant for footer edits in one specific way: if you change the footer and do not see the change on the front end, the cached version of the page is being served. The Hostney Cache plugin has a “Clear all caches” button that purges FastCGI along with any WordPress-layer caches in one click. After a footer edit, click it and then hard-refresh to see the change.

Automatic SSL and HTTP/3 delivery mean footer assets – social icons, logos, fonts referenced from the footer – load fast on the first visit, with the icon set and any inline SVGs arriving over a single multiplexed connection. And because every account runs in an isolated Podman container, editing a theme file cannot affect any other site, so child theme experiments are genuinely safe to try on production if you want to iterate live.

For anything more ambitious than a footer tweak – a complete theme rebuild, a multi-site rollout, or a staged change on a copy of the site – the file manager, Git deploys, and on-demand SFTP access cover the workflow without needing anything extra configured.