Browse Guides
Move to another guide without going back to the documentation hub.
Preview the Exact Widget You Plan to Publish
Use this page when you want to confirm what customers will actually see. The key rule is simple: Preview Page reflects the saved widget state, not temporary edits still sitting in the drawer.
Controls That Change the Preview
Use these controls to review the same saved widget across layout, device, and zoom states before you trust the hosted preview.
Save Changes Before Opening Preview Page
If the drawer still has unsaved edits, `Preview Page` stops and asks you to save first. That prevents you from reviewing an outdated widget by mistake.
What Preview Page Should Confirm
Use preview to answer three questions before publishing: is this the right layout, is this the right device state, and does the saved version still match what you expect to ship?
Layout mode
The hosted preview should show the exact saved List, Masonry, Grid, or Carousel layout you intend to publish.
Device state
Check both Desktop preview and Mobile preview so spacing, hierarchy, and review density still feel right on smaller screens.
Saved showcase output
If Preview Page does not match what you just edited, the most common reason is that the latest changes were never saved.
What Success Looks Like
The right layout appears
Preview Page should open the exact widget variant you chose, not an older saved layout.
Desktop and mobile both hold up
Check both preview modes before copying code so the live page does not surprise you on smaller screens.
No unsaved change is still pending
If the drawer was dirty, finish Save and Preview first before using the hosted result as the source of truth.
Spacing still feels balanced
Use the zoom selector to catch cramped cards, oversized gaps, or visual noise before anything goes live.
Need help?
Our technical team is available to assist with more complex integration previews and QA checks.
Contact Support TeamBefore you trust the preview
Save the latest changes, check both device modes, and make sure the hosted preview still matches the version you plan to publish.
Was this helpful?