Version scope: The UX Builder discussion below concerns Flatsome Classic. The newer Flatsome Site Builder uses a plugin and Block Theme with a different setup process. Check your package before following installation steps. See the developer’s product overview.
Looking for a Flatsome download? First identify the product you need. Flatsome Classic is the theme with UX Builder; the newer Site Builder uses a different installation and editing workflow. This guide explains the distinction, download sources and checks to make before changing a WooCommerce store.
We have worked on many e-commerce projects, and I can tell you that the theme foundation matters to the store’s day-to-day operation. That experience is a reason to test the editing and shopping workflows carefully, not a controlled benchmark showing that one theme is fastest.
What Flatsome Classic provides
Classic combines the UX Builder, Customizer-based header settings and WooCommerce-oriented layouts. UX Builder uses Flatsome elements and saves content as shortcodes. The developer also provides Flatsome Studio layouts. Check the available elements and account requirements against the package you intend to use.
A theme handles presentation; shipping, tax, payments and many specialist store functions still depend on WooCommerce and extensions. Test a variable product, cart and checkout with the plugins your business needs.
Classic and Site Builder are separate products
The developer’s Classic versus Site Builder comparison distinguishes the shortcode-based Classic editor from Site Builder’s block-based pages and template workflow. The products have separate licenses. Do not treat the Site Builder installer as an ordinary Classic theme update.
Before migrating, test custom code, templates and required features on staging. A Classic child theme and its hooks do not simply carry over to the new environment. Consult current migration documentation and review converted pages before applying a change.
Flatsome Classic vs. WooCommerce Storefront
Both can support a WooCommerce store, but they offer different starting points. This comparison concerns Flatsome Classic, the theme covered in this guide, not the newer Flatsome Site Builder product.
| Decision | Flatsome Classic | Storefront |
|---|---|---|
| Starting point | Premium theme with its UX Builder and store-oriented design tools. | WooCommerce’s free official theme, designed as a clean foundation for a store. |
| Editing | UX Builder uses Flatsome elements and saves its pages in its own shortcode format. | Uses the WordPress Customizer and can use blocks for custom landing pages; additional styling tools are available separately. |
| Best fit | Consider it if you prefer its integrated builder and prebuilt store design workflow. | Consider it if you want a free WooCommerce foundation and are comfortable building out your design. |
Test your real store, extensions and mobile checkout before choosing: neither option guarantees faster pages or higher conversion rates. Check the PureGPL Flatsome listing for its available version and supplier terms. Sources: Flatsome’s Classic and Site Builder comparison and WooCommerce Storefront documentation.
How to Download Flatsome: Choose the Correct Product
Check whether you need Flatsome Classic with UX Builder or the newer Site Builder. They have different installation paths.
- Flatsome Classic: use your ThemeForest downloads and select the installable WordPress file. The UX Themes update guide explains the package and update process.
- Flatsome Site Builder: follow the current developer installation guide. It starts with a plugin downloaded from your Flatsome account; its setup wizard installs the Block Theme.
- PureGPL listing: view the Flatsome package listing and check its product, version, update process and support terms before downloading. Do not assume that a third-party package includes a developer account or licence key.
This guide does not verify the contents or current version of third-party ZIP files. Product documentation checked on 28 October 2026.
Install or Update Flatsome Classic
- Back up your database and files before changing a working store.
- Get the installable theme ZIP, rather than an archive containing documentation and other files.
- In WordPress, open Appearance → Themes → Add New → Upload Theme and select the theme ZIP.
- Install it. For an update, confirm that you are replacing the intended theme; preserve custom code in a child theme.
- Clear caches and test the storefront after the change. Developer automatic updates require valid theme activation, as described in the linked UX Themes guide.
Installing the New Site Builder Instead?
Use Plugins → Add Plugin → Upload Plugin for the Site Builder ZIP, then follow its setup wizard. Check the developer’s current WordPress, PHP and WooCommerce requirements before starting. Do not upload the Site Builder plugin as a Classic theme.
Before Returning the Store to Customers
- Check the homepage, category pages and a variable product on mobile and desktop.
- Test product selection, cart totals, shipping and checkout on staging using your payment provider’s test mode.
- Check menu links and compare performance on the same URLs. A theme alone cannot guarantee a speed score or conversion rate.
Continue with our WordPress performance guide for a measurement plan.
Configure a Classic store after installation
- Complete the setup wizard where appropriate and confirm the product and license associated with your package.
- Open a page in UX Builder and build a small sample layout before importing a large demo.
- Set global branding and header options through the Customizer. Replace all sample links, text and images.
- Configure WooCommerce products, shipping, tax and payment settings separately.
- Test mobile navigation, product variations, cart totals, checkout and transactional emails before launch.
Performance and maintenance
Use appropriately sized product images and enable optimization options one at a time. Avoid delaying the main above-the-fold image simply because a lazy-loading switch is available. Check whether another plugin already handles the same optimization.
Compare the same pages before and after a change, using equivalent content and hosting. This guide does not provide a controlled comparison proving Flatsome faster than Elementor, WPBakery or another theme. A theme’s features also do not establish a conversion-rate improvement.
Keep custom code in a suitable child theme and maintain a restorable backup. Review release notes and test updates with your store extensions. See the UX Themes update instructions for Classic’s supported process.
Frequently asked questions
Is UX Builder interchangeable with Elementor?
No. The editors use different elements and content formats. Choose based on the layouts, integrations and maintenance workflow you need, and account for migration effort.
Can I use Flatsome for a non-store website?
Classic can build ordinary pages as well as store layouts. Compare its builder with the simpler options available for your project before choosing it primarily for features you will not use.
Does a Classic license include Site Builder?
No. The developer identifies them as separate products with separate licenses. Check the current offer and account entitlements before purchasing.
Will every WooCommerce extension work?
Do not assume universal compatibility. Test the exact versions and workflows your store relies on, especially checkout, subscriptions, pricing rules and product options.
How do third-party downloads handle support and updates?
That depends on the supplier’s terms. Verify the package, update method and support scope. Receiving theme files does not establish access to a developer account, license key or direct support.
Choosing the right Flatsome product
Choose Classic when its existing UX Builder workflow fits your project or when maintaining an established Classic store. Evaluate Site Builder separately for a redesign or new site. Keep the download source, installed product and documentation aligned, and test the complete store before publishing changes.