Portability matchup
Flatsome vs Blocksy: A Builder in Transition Against a Block-First Theme
On September 30, 2026, Flatsome announced that its future is built on WordPress blocks. Blocksy has been built on them since 2019. So the real contest here is not features. It is where your pages will live, and what they cost to keep, five years from now.
October 10, 2026 · 10 min read
The short answer
Choose Blocksy if you want pages built in the block editor, a free theme with a capable header builder, and a yearly or lifetime license from $69 as of October 2026. Choose Flatsome if you run a WooCommerce store, want shop features in the theme for a one-time $59, and accept that UX Builder layouts do not travel.
On this page
- Two bets on the block editor, made seven years apart
- Flatsome against Blocksy on thirteen practical rows
- What happens to a page you built in UX Builder
- Licenses that age in opposite directions
- Store features: in Flatsome's box, in Blocksy's extension
- Where each theme keeps its speed switches
- Matching the theme to the site you actually run
- When blocks versus builders is the wrong fight
Two bets on the block editor, made seven years apart
Flatsome made its name with UX Builder, a drag-and-drop editor of its own that stores layouts in a format only Flatsome reads. ThemeForest shows 270,401 sales. Now UX-Themes is building a successor, Flatsome Site Builder, on core WordPress blocks and theme.json, and calls it a new beginning rather than an update. The Flatsome review tracks both products.
Blocksy, from CreativeThemes, arrived on wordpress.org in 2019 and says it was built from scratch to be fully compatible with the block editor. The free theme has more than 300,000 active installs and a 100/100 rating from 873 reviews. Many of its features ship in the free Blocksy Companion plugin, which Blocksy Pro then extends. The Blocksy review explains how the theme, Companion and Pro fit together.
A page builder is a lease on your layouts. The block editor is closer to owning them.
Flatsome against Blocksy on thirteen practical rows
| Flatsome | Blocksy | |
|---|---|---|
| Pricing (as of October 2026) | No free version; Classic $59 one-time on ThemeForest; Site Builder beta billed yearly per site | Free theme; Pro Personal $69/yr (1 site), Business $99/yr (10), Agency $149/yr (unlimited) |
| Owner and support | UX-Themes; ThemeForest buyers get half a year of support | CreativeThemes; staff answer free users on the wordpress.org forum |
| Speed approach | Images and backgrounds lazy-load through Smart Lazy Loading; vendor claims top ThemeForest speed | Performance panel in the Customizer; vendor says it is lighter than most similar themes |
| CSS/JS delivery | Vendor says CSS was written for minimum size; font and jQuery controls not documented | Dynamic CSS as a cached file or inline; no jQuery dependency in the 2.1.58 theme scripts |
| Builder model | UX Builder plus reusable UX Blocks; successor Site Builder uses core blocks | Customizer for global design; pages in blocks, Elementor, Brizy or Beaver Builder |
| Header builder and mobile menu | Theme Options holds a header builder, with phones handled in a separate Header Mobile panel | Three-row builder with desktop and mobile layouts; mobile header under 1000px; menu in an off-canvas panel |
| WooCommerce | Store tools ship inside the theme, Catalog Mode included | Shop and product options free; quick view, wishlist, off-canvas cart and filters need Business |
| Page builder fit | Designed for UX Builder; Elementor support not stated by the vendor | Starter sites for Gutenberg and Elementor; Brizy and Beaver Builder named |
| Block editor fit | Listed as Gutenberg optimized; full block support arrives with Site Builder | Native: built for the block editor from the first release |
| License terms and refunds | Each site registers its own purchase code; Envato refund rules apply; Site Builder refunds within 30 days | Yearly or lifetime ($199, $299, $499); 14-day money-back guarantee |
| Known issues | Outdated Woo template copies, purchase code conflicts, missing UX Builder screens | 2.1.50 broke some product pages, a fatal error on sites without Woo, header HTML stripped in 2.1.58 |
| Long-term risk | Two products in parallel; classic layouts locked to UX Builder | Many features depend on the Companion plugin; frequent entries in vulnerability lists |
| Exit cost | High: UX Builder pages are rebuilt by hand | Low for block content; builder pages carry that builder's exit cost |
Two rows decide most cases. If the WooCommerce row matters most, Flatsome has the stronger store toolkit for less money. If the exit cost row keeps you up at night, Blocksy's block-first design is the safer place to put years of content.
What happens to a page you built in UX Builder
Content is the part of a website you pay for again if you get it wrong. A Flatsome Classic page built in UX Builder is stored as Flatsome markup. Switch themes and that page stops rendering the way you designed it, because no other theme speaks the format. The cost shows up as a rebuild, page by page, whether the destination is another theme or a Next.js site.
UX-Themes knows this, which is why the Site Builder launch mentions moving Classic sites over. The details are still settling: UX-Themes' pricing page counts a Classic migrator among the included tools, yet the beta announcement talks about a migration plugin still to come. Until that tool ships and has been tested on real stores, treat the migration as a promise, not a feature.
Blocksy pages built in the block editor are core blocks, saved in the ordinary WordPress format. Change themes and the content survives, with styling to adjust rather than a rebuild. If you built with Elementor on top of Blocksy, the content is portable only as far as Elementor is. The Blocksy block editor guide and Blocksy with Elementor cover each path, and Blocksy to Next.js shows what a move involves.
Licenses that age in opposite directions
Flatsome built its reputation on a single payment: as of October 2026, $59 buys Classic on ThemeForest along with half a year of vendor support. Site Builder flips that to yearly billing sold directly by UX-Themes: $44.50 buys the first year for a single site (half the $89 list price while early access lasts, until October 14, 2026), then $45 per site per year per the pricing page. Five-site and ten-site plans start at $149.50 and $249.50. The Flatsome pricing page keeps both models straight.
Blocksy goes the other way and offers a lifetime option on every tier. As of October 2026, one site on Personal costs $69 yearly or $199 once; ten sites on Business cost $99 yearly or $299 once; Agency covers unlimited sites for $149 yearly or $499 once. The Business tier is where pro starter sites and the Shop Extra and Post Types Extra extensions begin; only Agency gets White Label. CreativeThemes does not state a renewal price on the pricing page, so ask before you plan around one. Details are on the Blocksy pricing page.
Refunds differ in a way that matters to a cautious buyer. Envato's rules for Flatsome Classic exclude change-of-mind refunds, while Blocksy and Flatsome Site Builder both offer a money-back window, 14 days and 30 days respectively. That means you can trial Blocksy Pro and Site Builder; Classic is a commitment.
The third option
Athena CMS, with AI agents on staff.
Not a theme and not a blank Next.js repo. The content system we put behind every custom site: plain fields, a real preview, every version kept, and AI agents that handle the chores a plugin only nags you about.
- PicassoImages
- ApolloSite analysis
- AresCompetitor watch
- PrometheusContent holes
- AtlasPage depth and structure
- DelphiAI search visibility
and 12 more agents. Two come with Athena; the rest are monthly add-ons.
Store features: in Flatsome's box, in Blocksy's extension
For a shop, Flatsome hands over more on day one. Mini carts, quick view, free-shipping bars and Catalog Mode are part of the theme, and the Flatsome WooCommerce guide covers them. The cost is upkeep: Flatsome Classic keeps its own WooCommerce templates, which WooCommerce flags whenever its versions move ahead of the theme's.
Blocksy's free theme adds Customizer settings for the shop archive and single product pages. The features shoppers notice come from the Shop Extra extension on the Business and Agency plans: quick view for products, a wish list, filter and cart panels that open off-canvas, a floating add-to-cart bar and a slider for gallery thumbnails. The Blocksy WooCommerce page maps each to its plan.
Both have had store trouble lately. On wordpress.org, owners reported that Blocksy 2.1.50 pushed product details below an overlapping gallery on single product pages, fixed by rolling back. Flatsome owners more often meet checkout and template warnings after WooCommerce releases. Our notes on Blocksy WooCommerce layouts and Flatsome checkout issues cover the checks.
Where each theme keeps its speed switches
Blocksy puts its performance controls in one place: Customizer > General Options > Performance. Dynamic CSS Output can write a global.css file (the recommended mode) or print inline. The same panel can drop the emoji script, keep Gravatars on your own server and switch on native lazy loading for theme images. Local Google Fonts is a Pro extension. The Blocksy speed guide and the fix for Blocksy CSS that will not update go deeper.
Flatsome's documented lever is Smart Lazy Loading for images and backgrounds, set under its Advanced options. The vendor publishes PageSpeed and GTmetrix figures on its homepage but marks them as not a measured audit. Site Builder's launch post promises a big jump in page speed and less layout shift; that is the vendor talking about a beta. The Flatsome speed guide lists what to test on a real store.
Header and mobile menu habits differ too. Blocksy switches to its mobile header below 1000 pixels, opens the menu from a Trigger element into an off-canvas panel, and offers no breakpoint setting. Flatsome configures the mobile sidebar menu under Theme Options > Header > Header Mobile. If either menu stops opening, see Flatsome mobile menu fixes or Blocksy mobile menu fixes.
Matching the theme to the site you actually run
Pick Flatsome when
- Selling products is the whole point of the site
- You want shop features without a second license or extension
- A single $59 payment beats a yearly bill for this project
- You are willing to rebuild later if you ever leave UX Builder
- You want first access to Site Builder as a Classic customer
Pick Blocksy when
- Your editors write in the block editor and you want pages that outlive the theme
- You want a free theme with a real header builder before spending anything
- You would rather pay once than renew every year
- The store is modest, or Shop Extra covers what it needs
- You build for clients and want White Label on the Agency plan
New WooCommerce store, one site
Flatsome Classic, if you accept UX Builder lock-in. Otherwise Blocksy Business, which costs more but keeps the content in blocks.
Blog or content site with a small shop
Blocksy. The free theme carries the writing, and Shop Extra can be added when the shop grows.
Existing Flatsome Classic store
Stay put for now. Classic keeps getting compatibility and critical fixes. Revisit when Site Builder reaches 1.0 and its migrator is proven.
Agency building ten or more sites
Blocksy Agency. Unlimited sites and White Label beat buying a purchase code for every client.
Related matchups: Flatsome vs Astra for stores that want a general-purpose theme, GeneratePress vs Blocksy and Kadence vs Blocksy for lightweight rivals, and the comparisons hub for everything else.
When blocks versus builders is the wrong fight
This comparison assumes the site should stay on WordPress. For many shops and content sites it should. But some owners are choosing between two themes when the real constraint is the stack: a store that needs member pricing, a lead site that lives on load time, or a business that is tired of license keys, Companion plugins and update-day regressions.
A Next.js build sidesteps the theme question. Layout, routing and metadata are written in code, pages are built ahead of time and served from a CDN, and dependencies are pinned and tested before anything goes live. The trade is a larger first invoice and a developer for any change to structure, which we spell out in our Flatsome and Next.js comparison and the Blocksy version.
Owners still edit their own content in Athena CMS, which offers simple fields, a preview that matches the live page, a kept copy of every version, a built-in store and membership areas billed through Stripe. Apollo reviews each page and ranks the fixes; Aegis checks daily for intrusions. If you want to stay on WordPress and make it behave, our theme migration service moves sites between themes, and a free site audit shows which route is cheaper.
Questions people ask before they call
Neither vendor publishes a measured test of a real site, so nobody can honestly say. Blocksy gives you more documented controls: a cached CSS file, emoji removal, local Gravatars and lazy loading in one Performance panel. Flatsome documents Smart Lazy Loading. Build the same page in both on staging and test it yourself; our theme speed test guide shows how.
Not the pages built in UX Builder. They are stored in Flatsome's own format and need rebuilding in blocks or another builder. Posts written in the block editor move cleanly. Products stay in WooCommerce either way, though product page layouts change. Plan the move on staging with a list of every page. Our theme migration team does this work.
Yes, on every tier. As of October 2026 the one-time prices are $199 for Personal (one site), $299 for Business (ten sites) and $499 for Agency (no site limit). Flatsome Classic is a one-time $59 purchase on ThemeForest, while the new Flatsome Site Builder is billed yearly per site. See the Blocksy pricing page.
Not in a hurry. Site Builder entered beta on September 30, 2026, and UX-Themes says Classic will keep getting compatibility updates and critical fixes. The vendor's own pages disagree on whether the Classic migrator is included now or planned. Test it on a staging copy when version 1.0 arrives. The Flatsome review will track the change.
Agencies on wordpress.org have asked why Blocksy appears often in Wordfence weekly lists, and staff answered that fixes land before the reports go public. Our advice would be the same for any theme: keep it updated, test updates on staging, and watch for regressions like the 2.1.50 problems. If an update has already broken something, see Blocksy update broke my site.
Keep reading
- Store theme head-to-headFlatsome vs Astra for a WooCommerce Store: Who Builds the ShopFlatsome vs Astra for a WooCommerce store: shop features, checkout tools, license costs as of October 2026, known bugs, and which store each suits.
- Free tier against free tierGeneratePress vs Blocksy: The Patient Minimalist Against the Generous Free ThemeGeneratePress vs Blocksy: what each free version includes, how often each ships, header builders, WooCommerce, and prices as of October 2026.
- Blocksy in the block editorBlocksy and the Block Editor: A Gutenberg Site With No Page Builder PluginBlocksy in the block editor: Companion blocks, Advanced Posts with Dynamic Data, palette and widths, Content Blocks, and when to add a block plugin.
- Flatsome on phonesFlatsome Mobile Menu Not Working: Why the Sidebar Stays ShutFlatsome mobile menu not working? Check script optimizers, the Nav Icon, Menu Elements and the Main Menu - Mobile location, in that order, then fix it.
- Flatsome performanceFlatsome Speed Optimization: Product Grids, Lazy Loading and the Uncacheable CheckoutFlatsome speed optimization for store owners: Smart Lazy Loading, local fonts, UX Builder sections, cart and checkout that no cache can hold, in order.
- Theme review: FlatsomeFlatsome Theme Review (2026): Classic, the Site Builder Beta and Which One a Store Should BuyFlatsome theme review for WooCommerce store owners, checked October 2026: Classic vs the Site Builder beta, UX Builder, pricing, speed and who should skip it.
- Everything in WordPress Theme ComparisonsSee the section
Find out which theme your content can live with
Send us your site and what you plan to build next. We will tell you whether Flatsome, Blocksy or a custom build fits, and what a move would really involve.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.