The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
WordPress preview usually is not broken: it is showing an older saved state, a cached response, the wrong page or template, or content your account is not allowed to preview. Save the edit, choose View → Preview in new tab, refresh that tab, and test the URL while logged out. If the change is still missing, clear browser and WordPress/hosting caches, verify revisions and permissions, then check editor, theme and plugin compatibility.
Use the correct preview workflow first
The Block Editor and Site Editor both provide a front-end preview. The current interface supports Desktop, Tablet and Mobile widths plus a resizable canvas. In the post or page editor, open View and choose Preview in new tab. In the Site Editor, use the site-view option for the template or site area you are editing. WordPress documentation updated its preview guidance for WordPress 7.1 on August 19, 2026.
- Confirm that you are editing the intended post, page, template, template part or site.
- Save the change and wait until the save indicator finishes.
- Open View → Preview in new tab (or the Site Editor’s site view).
- Refresh the new tab after every subsequent save.
- Open the same URL in a private/incognito window or while logged out.
A preview tab is a loaded document; saving in another tab does not automatically replace that document. WordPress.com specifically advises saving and refreshing the preview tab whenever you want to see a newer version.
Recommended Free Tools
Why WordPress preview shows old or missing changes
The preview tab is stale
This is the most common explanation. Save, return to the preview tab and perform a normal reload. If a hard reload is needed, use your browser’s reload-without-cache command, then reopen the preview URL. Do not judge the result from an old tab that was opened before the latest save.
#1 Best Overall
- easy to use
- Free app
- Compatible with all devices
- It gives the best comparison between ten different hosts
Your browser cache is serving an older response
Browsers can reuse stored page data when a change appears small. Test in a private window first; that quickly separates a local browser problem from a site-wide problem. If the private window is correct, clear cached images and files for the site, close the old preview tab and open a new one. A local cleanup utility can help remove browser data, but it cannot purge a host, reverse proxy or WordPress plugin cache.
A WordPress, host, proxy or CDN cache is stale
WordPress itself does not include a cache by default. Caching normally comes from an installed cache plugin or hosting infrastructure. Managed hosts, reverse proxies such as Varnish, CDNs and optimization plugins may each retain a copy.
- Use the cache plugin’s Purge, Clear or Flush all command.
- Use the managed-host or CDN control panel to purge the affected URL or the full site cache.
- Ask the host which reverse-proxy and page-cache layers sit in front of the site and how to purge them.
- After purging, open a logged-out private window and reload the exact URL.
Purging a browser cache cannot fix a server-side copy, and purging a plugin cannot necessarily clear a host or CDN cache. Treat each layer separately.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteYou edited the wrong page, template or site context
Block themes separate page content from Site Editor templates and template parts. The homepage may be assigned to a different page than the one you edited, or its appearance may come from a template that overrides the page content. Confirm the preview URL, page assignment, active template and template parts before changing code or disabling plugins.
- For a post or page, verify its title, slug, status and permalink.
- For a homepage, check which page is assigned under the site’s reading settings.
- For a block theme, inspect the template used by that URL and any header, footer or content template part.
- Preview the exact object you changed rather than the site’s generic home URL.
The change was never saved, or the wrong revision is active
Autosave and a saved revision are not the same thing. WordPress revisions store each saved draft or published update; an autosave is a separate revision and does not overwrite the post itself. Open Revisions, compare the timestamps and content, and restore the intended saved state when necessary. Then save again and refresh the preview.
Your account cannot preview the content
Unpublished content requires the relevant preview capability. If a colleague can preview a draft but you receive an access error or a blank response, ask an administrator to verify your role and draft-preview permissions. Test the same URL with an authorized account before changing themes or code.
The editor canvas differs from the front end
The editor is a working canvas, not a guarantee of pixel-identical output. Theme CSS, responsive breakpoints, template parts and front-end JavaScript can change the result. Use the new-tab preview and compare it while logged out at Desktop, Tablet and Mobile widths. A block that looks correct inside the editor can still be hidden, restyled or repositioned by front-end rules.
A plugin, theme or editor mode is incompatible
Identify whether the site uses the Block Editor, Site Editor or Classic Editor. If the problem occurs only in one interface, record WordPress, theme and plugin versions before changing production settings. Temporarily compare with a default theme or a minimal plugin set on a staging site. The official Classic Editor plugin can restore the previous editor and Edit Post screen, making it a controlled compatibility check; it should not be treated as a universal fix.
Diagnostic order that minimizes risk
- Confirm context: match the edited object to the preview URL, template and homepage assignment.
- Confirm save completion: wait for the editor’s saved-state indicator; do not rely on an autosave.
- Reopen preview: choose View → Preview in new tab, then refresh after saving.
- Separate session effects: test in a private/incognito window while logged out.
- Clear local data: remove the site’s browser cache and reopen the URL.
- Purge site caches: clear cache-plugin, managed-host, reverse-proxy and CDN layers that apply.
- Inspect revisions: compare and restore the intended saved revision if content reverted.
- Check capability: verify that the user can preview drafts and private content.
- Isolate compatibility: on staging, compare editor modes, the active theme and plugins while recording versions.
Choosing the right fix
| Fix | Scope | Reversible? | What it proves |
|---|---|---|---|
| Refresh or reopen preview | One browser tab | Yes | The tab was stale |
| Private-window test | One browser/session | Yes | Whether login state or local cache is involved |
| Clear browser cache | One device/browser | Mostly; sign-ins may be affected | Whether stored client data caused the old view |
| Purge plugin or host cache | Site-wide or a URL pattern | Yes, by rebuilding cache | Whether server infrastructure served an old copy |
| Restore a revision | That content object | Yes, through another revision | Whether the intended saved state was different |
| Change theme/plugins or editor | Potentially site-wide | Not always; use staging | Whether compatibility changes output or preview access |
Troubleshooting by symptom
“Preview shows my previous text”
Save again, refresh the preview tab, then test logged out. If the old text remains, purge browser and site caches in that order. Check Revisions before editing the text a second time.
“The preview is blank”
Verify the URL and permissions first. A blank result can be a failed load, a template with no output, a front-end script error or a cached failure. Try a private window, inspect the browser’s developer-console errors, and compare with a default theme on staging. Ask the host whether a proxy or security layer is returning an empty response.
“Preview opens an access or permission error”
Sign in with an account that can preview drafts, confirm the post status and ask an administrator to check the role’s preview capability. A public logged-out visitor cannot necessarily view an unpublished URL.
“Only mobile or tablet preview is wrong”
Compare the same page at all three preview widths and inspect responsive block settings, theme breakpoints and CSS media queries. A desktop result does not guarantee that a mobile-specific style or hidden block is correct.
“The editor looks right but the front end does not”
Trust the new-tab front-end view for visitor output. Check template parts, theme CSS, front-end scripts and optimization plugins; then retest logged out after purging caches.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you need a repeatable image or PDF of the public result instead of diagnosing an editor tab, ScreenshotNeo provides a website screenshot API. It accepts the page as a visitor, removes cookie/consent banners, newsletter popups and chat widgets before capture, and labels each response with page and billing verdict headers. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed. Its MCP server lets Claude, Cursor and other MCP clients call take_screenshot, get_page_info and capture_pdf.
Use the API documentation at https://screenshotneo.com/docs/ for all parameters. A minimal call is:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpEquivalent Python:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Equivalent Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo includes full-page and element captures, device presets, custom viewport and retina scale, PDF controls, HTML/CSS rendering, custom JavaScript and CSS, click and wait actions, selector hiding, request/resource blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed links, asynchronous webhooks, bulk capture of up to 100 URLs per call, usage reporting and an OpenAPI specification. Its parameter names are compatible with those used by other screenshot APIs, which can simplify migration.
The Free plan includes 1,000 screenshots each month with no card. Paid plans start at $5 for 3,000 shots; every feature is on every plan, and yearly billing gives two months free. Create a free ScreenshotNeo account to start without a card.
Best Value
- Free WordPress Hosting Guide Android Application. It Contains: A Brief Overview of WordPress Hosting, 9 Major Benefits of Managed WordPress Hosting.
- 5 Simple Steps to Choose WordPress Hosting, How to Maximize Your WordPress Hosting and Blogging Success, How to Choose the Best WordPress Hosting Provider, Optimize Your Blog with VIP Word.
- Press Hosting, What You Should Know to Choose the Best WordPress Hosting and Much More.
Preventing preview confusion
- Save before every preview check and refresh the preview tab after every save.
- Keep a note of the exact URL, template and editor mode under test.
- Use a logged-out private-window check before declaring a public page fixed.
- Document which plugin, host, proxy or CDN cache was purged.
- Make theme and plugin compatibility tests on staging, with versions recorded.
- Use revisions rather than repeatedly overwriting content when investigating a rollback.
Frequently Asked Questions
Does WordPress preview automatically update after I save?
No. The already-open preview document normally needs to be refreshed after the save.
Can a cache plugin be responsible even when WordPress itself is current?
Yes. WordPress has no built-in cache by default, but plugins and hosting infrastructure can serve an older response.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsAre autosaves the same as revisions?
No. Autosaves are separate revisions; they do not overwrite the post’s actual saved content.
Why test preview while logged out?
A logged-out request shows what a public visitor receives and removes editor-session effects from the diagnosis.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
