What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The quickest way to preview one WordPress post or page is to open it in the editor, select View, and choose Preview in new tab. Check the desktop, tablet, and mobile layouts, save any later edits, and refresh the preview tab. For theme, plugin, or site-wide changes, use a staging copy instead of relying on an individual page preview.

Preview a post or page in the WordPress editor

  1. Open the item. In the dashboard, go to Posts or Pages, then open the post or page you want to inspect.
  2. Open the preview controls. In the editor toolbar, select View.
  3. Launch the front end. Choose Preview in new tab. WordPress opens a separate browser tab using the active theme’s front-end formatting rather than only the editor canvas.
  4. Check responsive layouts. Use the desktop, tablet, and mobile presets. Where the interface allows it, drag the preview width manually to test sizes between those presets.
  5. Save and refresh after edits. If you change the content after opening the preview, save it first, then reload the preview tab. WordPress.com’s workflow uses Save draft for draft content and Save for published content.

A draft remains unpublished while you preview it. A published page’s preview lets you review proposed edits before saving them. It does not create a private copy of your entire website.

What to inspect in the front-end tab

  • Headings, lists, links, captions, and spacing after the theme’s styles are applied.
  • Featured images, galleries, video, embeds, and other media at each viewport.
  • Navigation, breadcrumbs, sidebars, footer widgets, and related-post blocks.
  • Buttons and forms: test keyboard focus, visible labels, and whether controls fit on a narrow screen.
  • Text wrapping, horizontal scrolling, clipped images, and elements hidden behind sticky headers.

Preview the site design with the Site Editor

Use the Site Editor when you are changing templates or global design rather than one article. It requires an active block theme.

  1. Open Appearance > Editor.
  2. Use the editor’s preview controls to inspect the template or site.
  3. Select View site to open the front end in a new tab.
  4. Before saving, review the list of affected changes.

Header, footer, navigation, and other shared template parts can be used by many pages. A change that looks correct on one URL may therefore alter the appearance of the rest of the site. Check representative post, page, archive, and 404 templates before publishing.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Preview drafts and published edits as a visitor

Draft content

In the classic editor, use the Preview button. In the block editor, use View > Preview in new tab. Keep the item as a draft until the text, media, links, and layout are ready.

Published content

For proposed changes to an already published page, preview the edits before saving. After saving, open a separate logged-out browser window or private window and visit the public URL. This verifies what an anonymous visitor receives, without your administrator toolbar, login cookies, or personalized content.

Do not treat a logged-in preview as proof that every visitor sees the same result. Caching, membership rules, geolocation, consent settings, and personalization can change the public response.

When a staging site is the safer choice

Use staging for changes whose risk extends beyond one post: a theme replacement, plugin update, PHP or WordPress version change, navigation redesign, performance experiment, or conflict investigation. Staging clones the site so you can test without experimenting directly on production.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What staging lets you test

  • Whether plugins work together after an update.
  • Template and global-style changes across multiple content types.
  • Menus, forms, commerce flows, redirects, and logged-in roles.
  • Database-driven features and migrations before synchronization.

WordPress.com staging

WordPress.com documents staging for its Business and Commerce plans. Its staging site is a clone decoupled from production, and its sync workflow lets you select changes to copy back. Review exactly what will be copied or overwritten before syncing. These plan and workflow details apply to WordPress.com and should not be assumed for every WordPress host.

Other hosts

Managed hosts may provide a staging button, while self-managed installations may require a host-created clone or a manual copy. Confirm how the host handles database synchronization, uploaded media, cron jobs, email, search indexing, and payment gateways. A staging URL should be protected with authentication or a no-index control so unfinished work is not exposed.

WordPress Studio temporary preview sites

WordPress Studio can create temporary hosted preview sites from local work for client or team feedback. The official developer guidance describes these previews as an early-feedback option for up to seven days; permanent access requires a hosting plan. Studio documentation also states a limit of up to ten preview sites per account. This is a sharing workflow, not a replacement for production-like staging and deployment testing.

Preview checklist before publishing

  • Confirm the title, slug, excerpt, featured image, author, and publication settings.
  • Open every important internal and external link.
  • Check desktop, tablet, mobile, and an intermediate width.
  • Test forms, embeds, downloads, menus, search, and interactive blocks.
  • Review headings and alt text; make sure text remains readable at high zoom.
  • Check the logged-out URL after publishing or after changing a published page.
  • Clear or bypass relevant caches when an old version appears.
  • For site-wide changes, test a staging clone and review the proposed sync operation.

Or skip the browser setup: capture a WordPress preview with ScreenshotNeo

ScreenshotNeo is a website screenshot API and MCP server. Give it a URL and it returns a PNG, JPEG, WebP, or PDF. For a preview review, first save the draft or staging page, then pass its accessible URL to the API. Cookie banners are accepted and removed before capture, along with more than 60 known consent platforms, newsletter popups, and chat widgets. Each cleanup step can be disabled.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Only clean shots are billed. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the result with X-Page-Verdict and X-Billed headers. ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

cURL

See the complete parameter list in the ScreenshotNeo documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/preview -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com/preview"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/preview' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const body = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', body));

Useful options for WordPress review

  • Full-page capture loads lazy images; element capture can target a selector such as the article container.
  • Choose a device preset or any viewport, then use retina scale for sharper review images.
  • Set dark mode, timezone, geolocation, custom headers, cookies, user agent, or Authorization when the preview depends on them.
  • Wait for a selector, a delay, or network idle; click an element before capture; hide selectors; and block ads, trackers, requests, or resource types.
  • Use PDF paper size, margins, landscape mode, and page ranges for review packets.
  • Use HTML/CSS-to-image, custom JavaScript, transparent backgrounds, resizing, chosen cache TTLs, signed public image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, the usage API, and the OpenAPI specification when integrating reviews into CI.

Its parameter names also match those used by other screenshot APIs, which can simplify a migration. Plans include 1,000 shots per month free with no card, Starter at $5 for 3,000, Growth at $15 for 15,000, Pro at $39 for 60,000, Scale at $99 for 250,000, and Business at $249 for 1,000,000. Yearly billing provides two months free, and every feature is included on every plan. Create a free ScreenshotNeo account to start with 1,000 screenshots a month and no card.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Troubleshooting preview problems

The preview shows old content

Save the latest draft or published edit, refresh the preview tab, and clear a page or CDN cache if necessary. A logged-in editor may also see a different cached response from an anonymous visitor.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The preview URL redirects or returns a login screen

Check whether the page is private, password-protected, membership-restricted, or hosted on a staging domain requiring authentication. Use a logged-in browser for manual inspection, or provide ScreenshotNeo with the required headers or cookies when authorized.

Images or embeds are missing

Wait for the page to finish loading, verify the media URL, and inspect browser console errors. Lazy-loaded media may require scrolling or a wait condition; ScreenshotNeo’s full-page capture and selector waits address those cases.

A theme or plugin change breaks other pages

Stop testing on production, restore the last known-good state if required, and reproduce the change on staging. Check shared templates and plugin conflicts before synchronizing anything back.

The mobile layout overflows

Test an intermediate width, inspect fixed-width blocks and wide tables, and check images, embeds, and navigation menus. Fix the block or theme CSS rather than assuming the mobile preset represents every phone.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Frequently Asked Questions

Does previewing a WordPress draft publish it?

No. A draft remains unpublished until you explicitly publish it.

Can I preview the whole WordPress site at once?

The editor previews individual content or templates. Use a staging clone to evaluate broad site changes.

Why do I need a logged-out check?

Administrator sessions can hide caching, access-control, or personalization problems that anonymous visitors would encounter.

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.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.