You're planning a new website, and someone asks which platform you want. WordPress or Next.js? You search for an answer and find a dozen comparison articles. Almost all of them end the same way: "it depends on your needs."
That's true, but it doesn't help you decide.
Some of our client sites run on WordPress, and some run on Next.js, including our own. In this post I'll share how we actually choose between them, using three real projects as examples. The short version: the first question I ask has nothing to do with technology.
What's the first question I ask before choosing a platform?
"Who will update this website after launch?"
Most stack debates focus on speed, trends, or what developers enjoy using. Those things matter. But a website lives much longer than its build. What decides whether a platform was the right choice is what happens in month six, when someone needs to add a new page, swap a photo, or publish an update.
So before I talk about technology, I ask about people:
- Will your team edit content themselves, or will you send changes to us?
- How often will content change: every week, or a few times a year?
- Is the content mostly text and images, or is the visual experience the main point of the site?
The answers usually point to the right platform before we've discussed a single feature.
When does WordPress make sense?
WordPress makes sense when the people running the business need to manage the site themselves, without a developer in the loop.
Amata Architect, an architecture firm in Bali, is a good example. An architecture studio's website grows with its work: new projects, new photos, new descriptions. We built the site on WordPress with the WPBakery page builder and the Impreza theme, and handled the contact forms with the Forminator plugin.
That setup means new project pages can be built in a visual editor, from layouts that already match the site's design. Nobody has to write code to keep the portfolio current. For a studio whose website is mostly a showcase of its projects, that independence matters more than anything else.
WordPress also brings a large ecosystem. Forms, SEO tools, and other features are often a plugin away, which keeps build time and cost reasonable.
When does Next.js make sense?
Next.js makes sense when the experience itself is the product: custom design, smooth interaction, and full control over how every page looks and loads.
Our own website, Jupitr Tech, runs on Next.js. I designed it in Claude Design and developed it in Claude Code. For an agency, the website is the first piece of work a client sees. We wanted complete control over layout, motion, and performance, without working around a theme's limits.
Bali Trekking Exploration is the second example. The project covered a rebrand, a redesign, and a full redevelopment. I designed the new logo, designed the site in Claude Design, and built it end to end in Claude Code with Next.js. The site includes tour listings with filters, so visitors can narrow down treks quickly. Building that as custom components meant the filtering and the visual style could work exactly the way the brand needed.
In both cases, the visual experience mattered more than having a page builder. That's usually the signal for Next.js.
How do we decide at Jupitr?
We start with two questions, in this order. The first is about people. The second is about the experience.
If your team will edit content often, WordPress usually wins. If not, and the visual experience is the point, Next.js gives us the control to build it properly. If neither answer is strong, both platforms can work, and budget and upkeep become the deciding factors.
What are the honest trade-offs?
Neither platform is better across the board. Each one solves a different problem, and each one has a cost.
| What to compare | WordPress | Next.js |
|---|---|---|
| Who edits content | Your team, through a visual editor | Usually a developer, unless a content system is added |
| Design freedom | High, but shaped by the theme and page builder | Full control over every detail |
| Speed and performance | Good with care; page builders and plugins can add weight | Fast by default, since only what's needed gets built |
| Ongoing maintenance | Regular updates to WordPress, the theme, and plugins | Fewer moving parts, but changes need a developer |
| Features | Many available as plugins | Built as custom components to fit the project |
| Best fit | Content that changes often, managed by the client | Brand-led sites where the experience is the point |
The cost of WordPress is upkeep. Plugins and themes need updates, and every page builder adds some weight to the page. The cost of Next.js is independence. Without an editing layer, even small text changes usually go through a developer. Knowing which cost you'd rather carry is most of the decision.
Frequently asked questions
Is Next.js always faster than WordPress?
Not always, but it's fast by default. A well-built WordPress site can perform well too. The difference is that WordPress needs more care, because themes, page builders, and plugins can each add weight.
Can I update a Next.js website myself?
It depends on how it's set up. Without a content management layer, changes usually go through a developer. That said, some clients want to learn, and on request we teach them how to make updates themselves. We're happy to walk them through the best practices so the site stays in good shape. If you need to edit content often, tell us early so we can plan for it, or consider WordPress.
Is WordPress outdated?
No. It still powers a large share of the web, and it's a solid choice when your team manages content day to day. What matters is building it well: a good theme, only the plugins you need, and regular updates.
Which one is better for SEO?
Both can rank well. SEO depends more on structure, content, and technical health than on the platform. On WordPress we use Yoast for metadata and schema. You can check your current site's technical side with our free audit tool.
Which one costs more?
It depends on scope, not just the platform. WordPress can be quicker to build when existing themes and plugins cover what you need. Next.js often takes more custom work up front, but has fewer plugins to maintain later.
Can I switch platforms later?
Yes, but it's a real project, not a quick change. Content, design, and features all need to move. That's why it's worth asking the right questions before the first build.
I'm still not sure which one I need. What should I do?
Start with the question in this post: who will update the site after launch? If you're still unsure after that, we're happy to talk it through.
Next steps
You don't need to pick a platform today. Start with the people side.
- Answer the first question. Who will update your website after launch, and how often? Write it down before you talk to any developer.
- Check your current site. If you already have a website, run it through our free audit tool to see how it holds up technically.
- See both approaches live. Amata Architect runs on WordPress, while Jupitr Tech and Bali Trekking Exploration run on Next.js. Browse our portfolio for more of our work.
- Talk it through with us. If you're weighing WordPress against Next.js, get in touch with Jupitr Tech. We'll ask the questions above and recommend what fits, even if it's the simpler option.
