This question comes up constantly in WordPress development circles and the answers are usually useless — generic pros and cons lists that end with "it depends on your needs." Not helpful if you're actually trying to make a decision on a real project.
I've shipped projects with both. Here's how I actually think about this.
The decision is usually not yours to make
Let's get this out of the way first. In most agency setups the tool is already decided before you touch the project. The agency has a stack, a preference, a team trained on one tool — and they'll tell you upfront whether it's WordPress blocks or Elementor. Your job is to execute well with whichever one it is.
That said, when the decision is yours — on freelance projects, personal projects, or when an agency genuinely leaves it open — this is how I think through it.
What Elementor gets right
Elementor is my default preference, and the reason is straightforward: the development experience is clean.
Everything lives in one place. Controls, styles, responsive settings, widget registration — it's all organized, predictable, and consistent. When you build a custom widget you define the controls, write the render method, and you're done. The backend and frontend are separate concerns. You don't spend time trying to make the editor view match the frontend output — that's Elementor's job, not yours.
For clients, the editing experience is also genuinely good. The drag-and-drop interface is visual and intuitive. Non-technical users can manage their content without breaking layouts. That matters on projects where the client will be updating the site themselves long after delivery.
Custom widgets follow a consistent structure — content controls in one tab, style controls in another, responsive settings built in. Once you've built a few you have a pattern that scales to any section in any design. The barrier to entry for complex, design-accurate sections is low once the pattern is established.
What the WordPress block editor gets right
The block editor's strongest argument is that it's built into WordPress core. No additional plugin dependency, no third-party company making decisions about your client's site. The blocks you build are part of the WordPress ecosystem — they work with Full Site Editing, they work with patterns, they work with whatever direction WordPress core goes.
Block patterns are also genuinely useful. You can define reusable layout templates that editors can insert with one click — a feature Elementor hides behind a Pro subscription or requires a custom solution to replicate. For content-heavy sites where editors are creating new pages regularly, patterns are a significant time saver.
Performance is also a real advantage. The block editor adds significantly less overhead than Elementor. On projects where page speed is a hard requirement — ecommerce, high-traffic sites, performance-sensitive clients — blocks are worth the extra development friction.
Where the block editor falls short
The block editor is still reaching maturity. It has improved significantly over the past few years but it remains inconsistent in ways that Elementor isn't. The editor can be buggy. Breaking changes happen between versions. The team is actively developing it which is good long-term but creates friction in the short term.
The bigger issue for custom development is the boilerplate. Building a custom block requires block.json, edit.js, save.js, a build process, and careful attention to making the editor view match the frontend output. That last part is the real tax — the block editor's promise of "what you see is what you get" means you're responsible for making the editor look right, which takes time that has nothing to do with what the site actually needs to do.
For complex, design-accurate sections this friction adds up. Every custom block is more code, more build configuration, more editor-specific work compared to an equivalent Elementor widget.
How I actually choose
When the choice is mine, a few questions determine it:
How complex is the design? Heavily designed sections with custom components, specific layouts, design system integration — Elementor handles this more efficiently. Simpler content-focused designs work well with blocks.
How will the client manage the site? If the client will be creating new pages regularly, block patterns are worth the development investment. If the client mostly edits existing content, Elementor's editor is more intuitive for non-technical users.
Are there performance requirements? Hard page speed targets push toward blocks. Most projects don't have hard requirements and Elementor's performance is acceptable with proper setup.
What's the project timeline? Elementor is faster to develop with for custom work. If the timeline is tight and the design is complex, blocks are a harder sell.
My honest default is Elementor for most custom design projects. The development experience is smoother, the client editing experience is good, and the custom widget pattern scales well. I'd choose blocks when performance is critical, when the site is content-heavy with heavy editorial use, or when long-term independence from a third-party plugin is a priority.
Neither tool is categorically better. They solve slightly different problems and the right choice depends on what problem you're actually solving.