How to Put a New Joomla Site Offline While You Build It
Joomla has a built-in Site Offline setting for temporarily replacing the normal frontend with an offline page while you work. It is useful for a new site that is not ready for ordinary visitors, but it is not a substitute for server-level protection when the site contains sensitive information.
Turn Site Offline on
- Sign in to Joomla Administrator.
- Open System → Setup Panel → Global Configuration.
- Stay on the Site tab.
- Set Site Offline to Yes.
- Choose the desired Offline Message behavior. If you choose a custom message, enter text that tells visitors what they need to know without exposing private maintenance details.
- Optionally select an offline image if that suits the site.
- Select Save or Save & Close.
Verify what visitors actually see
Open the frontend in a private/incognito window where you are not already authenticated. The normal public site should be replaced by Joomla's offline page. Testing in a separate browser session matters because an authenticated administrator may be able to see the site differently from an ordinary visitor.
The offline switch does not disable the Administrator application. You can continue working in the backend while the frontend is offline.
Preview the site while building
If your account has the necessary permissions, Joomla can allow an authenticated privileged user to view the frontend while the public receives the offline page. Use a separate private window to keep a true visitor test available. Do not assume that because you can see the frontend, anonymous visitors can see it too.
When Site Offline is not enough
Joomla's offline mode is designed for temporary site availability control, not as a hardened staging-site security system. The offline page can expose the existence of the site and presents a login path. If a development copy must be private—for example, because it contains customer data, unreleased material, or production credentials—protect it at the web-server, hosting, VPN, or access-proxy layer as well.
Also consider search-engine exposure. If a hostname has already been publicly reachable, do not rely on an offline page to undo prior indexing. For a development environment, use a deliberate combination of access control and appropriate search-engine directives.
Do not confuse offline mode with disabling the site
Site Offline does not stop PHP, Joomla plugins, administrator activity, cron jobs, or every possible direct endpoint. It changes normal frontend availability. If you need a maintenance window where background processes must stop, handle those processes separately.
Bring the site online
- Return to Global Configuration → Site.
- Set Site Offline to No.
- Save the configuration.
- Open the site in a private/incognito window and test the home page plus several internal menu links.
- If caching or a CDN is in use, confirm visitors are not being served a cached offline page.
If the setting will not save
Global Configuration values are primarily stored in the site's configuration.php. If Joomla reports that configuration cannot be saved, investigate file ownership and writability rather than repeatedly toggling the setting. Avoid making the entire Joomla installation broadly writable as a workaround.
Verification checklist
- Anonymous visitors receive the intended offline page.
- Administrator remains reachable.
- Your privileged account can perform the work it needs to perform.
- Sensitive staging sites have stronger server-level protection where required.
- After launch, an anonymous browser can reach normal frontend pages.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.