The Editor Looks Different From The Site
The block editor is a working preview, not a pixel promise: it arranges your blocks in the theme's styles, but the front end adds behaviour and context the editor does not run. When the two differ, the difference almost always belongs to one of the causes below, so check them in order rather than assuming a defect.
JavaScript Runs On The Front End
Sliders, carousels, counters, filters and every scroll-driven behaviour are powered by front-end JavaScript, and the editor shows their static arrangement instead of running them. A carousel lays its items out as a strip you can scroll sideways in the editor, where every item stays selectable and editable, and animates on the site: both surfaces doing their job. Judge motion and interaction on the published page, not in the canvas.
The shared Animation panel is the sharpest case: a block with an entrance animation plays it on the front end when it scrolls into view, so the block's position and timing can only be judged live. The same goes for the Scroll Effects panel's parallax and fades.
The Chrome Is On The Canvas, With Two Exceptions
A page opens inside its template, so the header, the footer, the content wrapper and the slider or hero the page assigns are all on the canvas while you edit. If you are looking at the content alone, Show template is turned off in the page's Template panel, which is a preference of yours rather than a fault; turn it back on to see the page dressed.
Two things still differ from the front end. A header built in the Header Builder and an assigned Footer record are swapped in as the page is served, so the canvas draws the theme's own header and footer template part instead of that record: edit the record on its own screen and check the result on the site. And the chrome decides part of its own appearance out there. A transparent header renders in its solid scheme on a page with nothing sitting under it, no hero, no assigned slider and no title band pulled up behind the bar, and that check runs on the front end, so the editor and the Site Editor still preview the transparent version.
The License State Gates Premium Output
Premium blocks follow the license: on a site where a license has never been activated they do not render on the front end, and an administrator sees a notice in their place while visitors see nothing. A block that is visible in the editor and absent from the page is the signature of exactly this. An expired license is different: the page keeps rendering in full, and only editing premium blocks pauses. Check Canvas > License and see License Problems.
Colours Follow One Palette
The colours Canvas components use and the colour palette in the Site Editor's Styles are one set of values. Changing a palette colour in Styles, or choosing a style variation, recolours Canvas buttons, links, menus and every other component keyed to that colour, in the editor preview as you make the change and on the site once you save. The Theme Color swatch is the same value as Primary Color in the Color Scheme tab of Canvas > Theme Options, so a change in either place shows up in the other. If the site and the editor disagree about a colour, save the Styles change first; an unsaved change exists only in the editor. The Custom Color Presets and Gradient Presets on the Color Presets sub-tab of the same Theme Options tab join the editor's colour and gradient pickers too, so a preset you add there can be chosen on any block.
A colour setting in Theme Options takes a hex value such as #1abc9c. A value that is not a valid colour is refused, and the setting keeps the colour it had, or its default when it never had one, so a typing slip cannot blank a brand colour. The same rule applies to a colour set with wp canvas option set.
Fonts Follow The Same Chain
The fonts you choose in Theme Options and the fonts in the Site Editor's Styles are one set, exactly as the colours are. The families you load on the Typography screen of the Canvas menu appear among the font families in Styles, and the Headings Font and Body Font on the Typography tab of Canvas > Theme Options become the Primary and Body font families there. Changing the Headings or Text font in Styles and saving changes Canvas text on the site, not only WordPress's own blocks. A later font change in Theme Options points Styles back at that new choice, so the newer decision always shows.
Font family and weight in Theme Options start on Theme Default, which follows the active design. Leave them there to keep a demo's fonts: saving Theme Options no longer freezes whatever the screen happened to display, so a site built on a demo keeps its typography until you pick a font yourself.
With Host Google Fonts Locally switched on, on the Loading & Fonts tab of Canvas > Performance, the site's Google fonts are installed into WordPress's Font Library and served from your own site, so visitors' browsers never contact Google for them. That covers the fonts set in Theme Options and those of a demo imported site wide. Canvas installs them when you save the option, and when the list is long it carries on over the next admin screens you open. Any other Google Fonts stylesheet a page still loads, such as a page scoped demo's, is served from a copy Canvas keeps in your uploads. Switching the option off deactivates the fonts Canvas installed.
Site Editor Styles Reach The Site
Changes made under Styles > Blocks in the Site Editor, and the Additional CSS you add there, apply on the front end as well as in the editor. Canvas removes only WordPress's default spacing rules between blocks inside its layouts, because the design supplies its own spacing, and it keeps them too once you set a Block spacing value in Styles.
Quotes and separators take their look from the Canvas design itself, so choosing a style variation recolours the palette without restyling them. A style you set for the Quote or Separator block under Styles > Blocks still applies.
Caching Serves Yesterday's Page
A page cache, a CDN or an optimisation plugin can keep serving the page as it was before your edit, which reads as "the editor has my change and the site does not". Clear the site's cache and hard-reload the browser before investigating anything else, because this cause is the cheapest to eliminate.
Pitfalls
A section is invisible on the front end but present in the editor. Check three suspects in order: an entrance animation waiting for the section to scroll into view, a premium block on an unlicensed site, and a visibility utility class left in the block's Additional CSS class(es).
The menu shows an instruction row in the editor that is not on the site. A Canvas Header Navigation block with no menu assigned draws "Assign a menu in the block settings" while you edit, because that row is a message for you rather than for a visitor. The front end renders an empty menu in its place, so assign a menu and both surfaces fill.
Fonts differ between editor and site. The editor loads the theme's fonts, but a font registered by an imported demo applies through that demo's styles, so compare on the front end of a demo-styled page before changing typography settings.
Spacing differs at the page edges. The page template and its content wrapper are on the canvas, so edge spacing usually matches. Per-page layout classes are a different matter: they are applied as the page is served, so a page that overrides its wrapper that way is best judged on the preview.
What To Read Next
- Controls Every Canvas Block Has, the Animation, Scroll Effects and Advanced panels this page keeps referring to
- Getting Support, if the difference survives every check above
