When a website consists of multiple pages, it will usually have shared files for headers, footers, menus, and other elements used across those pages.
If you modify only one page and want to update the public site, use Apply Changes for that page.
When you modify a shared file, however, the changes must be reflected on every page that uses it. Instead of applying the changes to each page individually, you can use Apply Changes to All Pages.
Apply Changes to All Pages is available from the Page menu in the editor.

Why “Apply Changes to All Pages” Is Needed
A webpage may be built from more than one page file.
For example, an About page might use the following files together.
About page file
+ Layout containing the header and footer
+ Menu component
+ Shared CSS
+ Shared JavaScriptIf you modify only the content of the About page, the scope of the change is limited to that page.
However, when you modify a file used by other pages, such as a layout or component, every page that uses that file is affected.
A shared file exists only once in the project, but the public site contains the generated result for each page that uses it.
After modifying a shared file, you must therefore apply the changes again to every page that uses it. Apply Changes to All Pages lets you apply changes from shared files to all published pages at once.
“Apply Changes” and “Apply Changes to All Pages”
Use Apply Changes or Apply Changes to All Pages according to the scope of the change.
| Feature | When to use it |
|---|---|
| Apply Changes | When applying changes to a specific page |
| Apply Changes to All Pages | When applying changes from shared files to all published pages |
For example, if you only modified /public/about/+page.essepage, use Apply Changes for that page.
/public/about/+page.essepageIf you modified a layout used throughout the site, use Apply Changes to All Pages.
/public/+layout.essepageWhen to Use “Apply Changes to All Pages”
You may need to use Apply Changes to All Pages after modifying the following types of shared files.
Layouts
Layouts provide menus, headers, footers, and other common page structures used across multiple pages.
/public/+layout.essepageWhen you modify a layout, multiple pages using that layout are affected. Use Apply Changes to All Pages to apply the change.
Head Layout
The head layout provides a shared <head> for every page.
/public/+head.essepageUse Apply Changes to All Pages after modifying shared metadata, external stylesheets, or the structure that connects page titles and descriptions.
Components
When you modify a component used across multiple pages, such as a menu, button, or card, every page using that component is affected.
/components/navigation.essepageUse Apply Changes to All Pages to apply changes from shared components across the public site.
Imported or Included Files
Modifying HTML, CSS, or JavaScript files imported or included by multiple pages can also affect those pages.
/styles/site.css
/scripts/site.jsIf the modified file is used by multiple pages, use Apply Changes to All Pages.
Shared Configuration and Global Variables
Changing configuration or global variables used by multiple pages may affect every page that uses those values.
After modifying shared configuration included across the site, check the affected pages and use Apply Changes to All Pages.
When “Apply Changes to All Pages” Is Not Needed
You do not need to use this feature for every change.
If you only modify content on a specific page, use Apply Changes for that page.
/public/about/+page.essepageFor example, changing only the heading or paragraph on the About page does not affect other pages.
<h1>About Us</h1>
<p>Learn more about our company.</p>In this case, use Apply Changes for the About page file.
Applying Changes to All Pages
Once you have checked the shared file changes, apply them to all pages.
- Save all modified files.
- Preview the affected pages.
- Open the Page menu in the editor and select Apply Changes to All Pages.
- Wait for the operation to finish.
- Check the main pages on the public site.
Apply Changes to All Pages does not save your files. If you have unsaved changes, save the files first.
The cache may take some time to update immediately after applying changes to all pages.
If the public page still displays the previous content, wait a moment and refresh it. For more information, see Cache and Update Timing.
Next Steps
Once you understand how to apply changes to all pages, continue with the following guides.
- Understand the difference between saving, publishing, and applying changes: Save, Publish, and Apply
- Connect a domain to your site: Custom Domains
- Learn when changes appear on the public site: Cache and Update Timing
- Check available capacity and features: Limits and Usage
- Manage shared page structures: Layouts
- Manage reusable elements: Components