Blocksy and Elementor: What the Theme Changes Inside the Builder, and How to Set It Up

Five version numbers on one Blocksy and Elementor site

A typical Blocksy and Elementor site runs the Blocksy theme (2.1.58, released October 2, 2026), the Blocksy Companion plugin (also 2.1.58, released a day earlier), often Blocksy Pro, Elementor (4.3.4, released October 5) and often Elementor Pro. That is five products, two vendors and five changelogs, all of which have to agree before a page renders correctly.

Blocksy's own review history shows why that matters. The 2.1.50 release broke single product layouts for some WooCommerce stores and threw a fatal error on some sites without WooCommerce. The 2.1.58 release began stripping input elements from the header builder's HTML element. Add Elementor's own release pace and you have a site where Tuesday's update can come from any of five directions.

Blocksy plus Elementor is a good stack with a long changelog. Read it before you click Update.

So the first setup step is not a setting. Write down the five version numbers that currently work, keep a staging copy, and update the Blocksy pieces together, then Elementor, testing in between. Blocksy update broke my site has the rollback routine when a release misbehaves.

What Blocksy changes inside Elementor without asking

Blocksy has no help article about Elementor; the integration URL we tried returns nothing. The theme's code does have an Elementor integration file, and reading it in version 2.1.58 shows exactly what Blocksy adjusts when Elementor is active. None of it is harmful. All of it explains behavior that otherwise looks like a bug.

The breakpoint row is the welcome surprise. Blocksy's CSS shows the mobile header below 1,000 pixels and a mobile breakpoint at 689.98, and the theme nudges Elementor to match. The catch is the phrase if they have not been set. On a site that ran Elementor before Blocksy arrived, Elementor's existing values, 1,024 and 767 by default, stay put, and the header and content switch at different widths. Check Site Settings > Layout > Breakpoints and set 1000 and 690 yourself if needed.

Full-width Elementor pages when Blocksy has no full-width structure

Blocksy's per-page panel, titled Blocksy Page Settings in the block editor sidebar, has a Page Structure setting with Inherit, Narrow Width, Normal Width, Left Sidebar and Right Sidebar. There is no Full Width choice. That surprises owners coming from Astra or Kadence, and it means a full-bleed Elementor page needs a slightly different recipe.

1. 1

   Content Area Style: Wide

   Set Content Area Style Source to Custom, then choose Wide, so the content area blends into the page background instead of sitting in a Boxed container.

2. 2

   Content Area Vertical Spacing: Disabled

   Set the source to Custom and pick Disabled. The other choices are Top and Bottom, Only Top and Only Bottom.

3. 3

   Page Title: Disabled

   The Page Title panel takes Inherit, Custom or Disabled. Disable it when the Elementor hero carries the H1.

4. 4

   Let Elementor do the stretching

   Use full-width containers inside Elementor. If the content still stops at the container edge, Elementor's Elementor Full Width page layout keeps Blocksy's header and footer while laying the content across the screen.

5. 5

   Set it once in the Customizer

   Customizer > Pages holds the site-wide defaults for title, content style and spacing, so pages inherit instead of being set one by one.

The same panel's Page Elements group has Disable Featured Image, Disable Share Box, Disable Header and Disable Footer. There is no per-page transparent header switch. Transparency is a Companion feature set in the header's Customizer options, with Transparent Header Display Conditions choosing which pages get it. If a transparent header turns up on an Elementor landing page by surprise, those conditions are why.

Headers, footers and templates: three owners to choose from

Blocksy's free header builder is the reason many people install it: three rows, separate desktop and mobile layouts and a Trigger element that opens the off-canvas mobile menu. Blocksy Pro adds conditional headers and Content Blocks, which include Header and Footer templates alongside hooks, pop-ups, single, archive, 404 and maintenance templates, all driven by a Conditions module. Elementor Pro's Theme Builder can build headers too, and Blocksy registers its locations, so an Elementor Pro header will replace Blocksy's where conditions match.

• Blocksy's header builder: our default. Free, light, and the mobile menu belongs to the theme.
• Blocksy Pro Content Blocks: right for hooks, pop-ups and conditional templates. Blocksy's current docs open them in a Gutenberg canvas, though the hooks doc mentions using your favorite page builder; test Elementor editing on your version before planning around it.
• Elementor Pro Theme Builder: right when designers build every layout in Elementor and want its conditions in one place.

Never run two of them for the same location. When both an Elementor Pro header and a Blocksy conditional header claim the shop, owners edit one and see the other. Menu problems on phones are covered in Blocksy mobile menu not working, and if custom HTML in the header lost its form fields after 2.1.58, that is the release's known change rather than Elementor.

Colors flow one way; fonts depend on what you paid for

Blocksy's Colors panel, under Customizer > General Options > Colors, holds a Global Color Palette of eight colors plus any you add, each with a CSS variable. Blocksy's docs say the palette is integrated with supported page builders such as Elementor, and the code confirms it arrives in Elementor's global colors. It is one-directional: change a color in the Customizer and Elementor follows; there is no path back. That is the safer design, because the brand lives in one place.

Fonts are less tidy. Blocksy's Local Google Fonts extension is a Pro feature, so a free Blocksy site loads its Customizer typography from Google's servers. Elementor has its own Load Google Fonts Locally setting, free, which covers fonts chosen inside Elementor widgets. If the theme and the widgets use the same family, a free site can end up with one copy local and one from Google. Either buy Pro and host fonts through Blocksy, or set typography in one tool and inherit it in the other. Blocksy speed shows how to confirm what each page actually downloads.

Two CSS caches, one update routine

Blocksy's Dynamic CSS Output, under Customizer > General Options > Performance, writes a generated global.css file by default (the vendor's recommended mode) or prints the styles inline. Elementor's CSS Print Method also writes external files by default. Both are good for speed. Both can hold stale styles after a change, which is why a color edited in the Customizer sometimes refuses to appear on an Elementor page.

• Clear in order: regenerate Blocksy's CSS, then click Clear Files & Data under Elementor > Editor > Tools, then purge the page cache and any CDN.
• Isolate before blaming: Elementor's Safe Mode, on the same Tools screen, loads the editor without the theme. If the editor works there, the theme or a plugin is involved; the full routine is in Elementor theme conflicts.
• Turn off what Elementor duplicates: Blocksy's Performance panel can disable the emoji script and lazy load theme images; Elementor's Optimized Image Loading handles the images it places.
• Watch the add-ons: most weight on these sites comes from Elementor containers, widget styles and add-on packs, not from Blocksy, whose theme ships no jQuery-dependent scripts.

Stale styles specifically are covered in Blocksy CSS not updating. For stores, the 2.1.50 product layout regression has its own page: Blocksy WooCommerce layout broken.

Starter sites: pick the Elementor version only if you mean it

Blocksy offers starter sites built for Gutenberg and for Elementor, and many designs come in both. The import decides your content tool for years, so it deserves more thought than the thumbnail. Choose the Elementor version if your team already owns and knows Elementor, or needs Elementor Pro features such as its form and popup builders. Choose the Gutenberg version if nobody has a strong preference, because Blocksy's own blocks, patterns and Content Blocks are designed around the block editor.

Imports stall often enough that Blocksy keeps a help doc for it, and support has said it cannot diagnose installs that are not publicly reachable. Import on a staging URL, not localhost. The block-editor route is described in Blocksy with Gutenberg, and plan pricing for the Pro starter designs is on Blocksy pricing.

When to drop Elementor, Blocksy, or both

Blocksy is a generous theme and Elementor a capable builder, and plenty of sites run the pair happily. The stack becomes the problem when its upkeep outweighs its output: five changelogs for a site that needs one form and a dozen service pages, or a store that cannot absorb a regression.

Dropping Elementor is the cheaper fix for many Blocksy sites. Leaving WordPress is the bigger one, compared fairly in Blocksy vs Next.js and page builders vs Next.js. Elementor content comes out of its stored JSON as described in Elementor to Next.js, and the theme side is in Blocksy to Next.js. If you are staying, our Elementor developers and theme troubleshooting service keep the stack honest. The Blocksy review and the rest of the WordPress themes section cover the alternatives, including Kadence vs Blocksy.