---
title: "Should I Publish to production for any content changes?"
slug: "should-i-do-a-push-to-production-for-any-content-changes-1"
updated: 2026-01-15T06:31:48Z
published: 2026-01-15T06:31:48Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.whatfix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Should I Publish to production for any content changes?

Yes, any content or settings changes require you to [Publish Whatfix Content](/studio/docs/publish-whatfix-content).

When you save a change, it gets saved on the Whatfix server. But, for your end users to see it, the change needs to be pushed across to the CDN they are using.

All changes, such as modifying Whatfix content, setting different visibility rules, or changing global configurations, might appear when you use the **Preview mode** or **See Live** mode. However, for the changes to reflect on your end users' application, you must publish changes.

Note:

Whatfix enables you to publish changes, such as **Global themes and configurations**, **User Actions**, and other account-level changes, without having to push any content or widget to production along with them.

Use the following steps to publish changes:

1. Go to the **Ready** stage and then click **Publish all.**

The **Publish changes** button is visible instead if the **Ready** stage is empty.

1. In the dialog box, review your changes, and then click **Publish**. 
     ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Selective_publishing.gif)

## Related

- [Publish Whatfix Content](/publish-whatfix-content.md)