RapidWeaver Elements vs Blocs

A practical comparison for choosing the right Mac-native visual website builder.

Both RapidWeaver Elements and Blocs are Mac-native visual website builders that export real website files. They share a similar goal, but they’re built on different foundations and tend to suit different workflows.

This comparison focuses on the day-to-day differences that matter when you’re building, maintaining, and scaling websites over time.

Quick take

Choose RapidWeaver Elements if you want:

  • A modern workflow with a built-in design system (Theme Studio).

  • A Node Browser to manage complex page structures cleanly.

  • A built-in Markdown CMS for blogs and content-driven sites.

  • Modern publishing targets (including Amazon S3), plus classic FTP/SFTP.

  • An extensible platform with Custom Components and a Developer API.

Choose Blocs if you want:

  • A Bootstrap-based workflow and the CSS Class Editor for visual class management.

  • Custom interactions and WordPress theme building (Blocs Plus).

Why people switch to RapidWeaver Elements (including former Blocs users)

Common themes from people who move to Elements:

  • A simpler workflow for building and maintaining sites: especially compared to setups that required lots of add-ons or became complex over time.

  • Clearer structure management via the Node Browser: which helps a lot on larger pages.

  • More consistent styling using Tailwind plus a built-in theming system, reducing the need to manage lots of custom classes.

  • Content workflows without a heavy CMS: Markdown files plus a built-in CMS are a good fit for blogs, portfolios, directories, and “update often” sites.

  • Modern publishing options: including static hosting targets, with fewer steps between “done” and “live”.

  • An active roadmap: frequent releases and responsive community support.

Where Blocs might be a better fit

Blocs is a strong choice when you specifically want:

  • Bootstrap-first layout: especially if you already think in Bootstrap’s grid and patterns.

  • The Class Editor workflow for quick: visual class-based styling and layout tweaks.

  • WordPress theme export: (Blocs Plus) as part of your delivery workflow.

Testimonial from Blocs User moving to Elements

I have bought Sandvox, Dreamweaver, Blocs 4, Sparkle (now Spritely), Rapid Weaver Classic (with Stacks and Foundry 2). I didn’t like ANY of them. All I wanted to do was easily redo my existing website using a recent and modern piece of software so that I could easily maintain and update it. I was not able to easily (or at all) do that with ANY of them. Until Elements…

I like Elements. I like working in Elements. I joined the beta almost exactly one year ago and have seen the massive improvements to it during that time period.

I can build stuff with Elements and enjoy it at the same time. That is why I am using Elements, and hope to use it for many years!!

Tips from Ex-Blocs Users

  • Elements’ Node Browser gives you a clear overview of your layouts, much easier than wrangling blocs and brics!

  • Tailwind theming just works in Elements, so you don’t have to fight with custom classes or inconsistent styles.

  • If you need a hand, the Elements Support Forum is super friendly, and you can always tag @elementsbot for help.

How to Switch from Blocs to Elements

Migrating from Blocs to Elements is a fantastic move if you’re looking for a modern, flexible, and genuinely fun web design experience. Elements was built from the ground up for rapid, future-proof site building with a fully WYSIWYG editor and the power of Tailwind CSS at your fingertips.

Here’s a detailed, step-by-step guide to help you make the switch:

Step 1: Prepare Your Content and Assets

Before you dive in, make a list of:

  • Pages you need to migrate

  • Content (text, images, videos)

  • Any custom code or integrations you used in Blocs

Export and organise images/assets so they’re ready to add into Elements.

Step 2: Set Up a New Project in Elements

  1. Open Elements and hit File > New Project.

  2. Choose a starting project or begin with a blank project.

  3. Set your global site settings (site title, address, and favicons) in the Site Settings menu (cog in the toolbar).

Step 3: Recreate Your Pages

For each page from your Blocs site:

  1. Click the “+” in the sidebar to add a new page.

  2. Name it to match your old site structure (e.g., Home, About, Contact, etc.).

  3. You can modify the file name and folder for each page in the page inspector.

Step 4: Rebuild Layouts Using Components

  • Drag and drop Components into your page(s) to match your old layouts.

  • Elements has built-in Components and pre-built Templates for common needs (navigation bars, galleries, buttons, etc.).

  • Arrange and customise each using the Inspector, change text, swap images, adjust colors, all visually.

Step 5: Style Your Site

  • Use the Theme Studio to adjust site-wide color palettes, fonts, and spacing.

  • If you want extra flair, take advantage of Tailwind utility classes directly in the advanced settings (but you never need to touch code if you don’t want to).

Step 6: Rebuild Forms & Integrations

  • Drop in the Form Component for contact/newsletter pages.

  • Configure field types, labels, and actions visually.

  • Point form actions to your email or third-party service; Elements supports customizable form actions.

Step 7: Preview and Publish!

  • Preview your site in the browser by pressing Cmd + P or the browser icon in the toolbar.

  • If you're site looks good, feploy to your host via the built-in publishing engine.


If you have any specific component or layout you’re struggling to recreate, just ask on the forum. Share a screenshot or describe what you need and we'll guide you to the best solution in Elements.

Welcome to the future of Mac web design, the Power of Elements is waiting for you!

Last updated

Was this helpful?