Themeisle's light theme, tested
Neve vs Next.js: A Featherweight Theme Against a Custom Build
The checkout page says $69. The renewal notice, a year later, says $139. Between those two numbers sits most of what you need to know about Neve: a genuinely light free theme with a Pro plugin that grows, quietly, into a yearly line item.
October 7, 2026 · 11 min read
The short answer
Neve is a strong pick for a small blog, service business or simple store that wants a fast free theme and Customizer controls. Next.js is the better fit once the site drives leads at scale, needs custom features or must stay fast as plugins pile up. Neve costs less to start; Next.js costs less to keep fast.
On this page
- What 28 kilobytes buys, and where the count stops
- Six months later: Pro, a starter site and five more vendors
- Where Neve wins and loses, line by line
- Introductory pricing and the second invoice
- Where Neve sites come apart
- Two honest lists for a Neve owner
- Why a Neve site packs up more easily than most
- Simple editing without a yearly Pro renewal
- Blogs, service firms and small shops: our call on each
What 28 kilobytes buys, and where the count stops
Credit first, because Neve earns it. The free theme has 200,000+ active installs on WordPress.org and an average rating of 94 out of 100 across 1,283 reviews. It asks for little: PHP 7.0 and WordPress 5.5, which means almost any host will run it. Themeisle shipped version 4.2.15 on October 1, 2026, so the free theme is not gathering dust.
The vendor says a default Neve install weighs 28KB and loaded in 0.6 seconds in its own test. Those are Themeisle's numbers, measured on Themeisle's setup, and you should read them as a ceiling on how light the theme starts rather than a promise about your homepage. What is verifiable is the toolset. The drag-and-drop header and footer builder is free. Local hosting of Google Fonts is free too, under Neve > Dashboard > Settings > Performance, and it also localizes fonts that other plugins load. Few free themes give away that much.
The catch is in the word *default*. Nobody runs a default install. The count stops at the theme, and the Neve speed guide explains which settings matter once the real site arrives on top of it.
Six months later: Pro, a starter site and five more vendors
A Neve site rarely stays a theme and nothing else. The usual path looks like this, and every step is reasonable on its own day.
- A starter site goes in first. The Business plan's 110+ starter sites import pages, images and settings in one pass, which is fast until an import half-finishes and you need help with a failed starter site import.
- Neve Pro arrives as a plugin. Custom layouts and hooks, the extended header components and the Performance extras all live in the add-on, not the theme.
- A page builder or a block plugin joins. Neve works with the block editor, Elementor, Beaver Builder, Brizy and others; Themeisle's own Otter Blocks is the house option, and Otter Blocks Pro comes with the Agency plan.
- WooCommerce brings Booster features. Quick view, wishlist, comparison and variation swatches are Business-plan modules layered onto the store.
- Then the usual tenants move in. A caching plugin, an SEO plugin, a form plugin, a security plugin and often a host-supplied optimizer.
Five vendors, five update schedules, one Customizer. That last plugin, the host's optimizer, is the one that showed up in a June 2026 support thread about the mobile menu, which we cover below.
Where Neve wins and loses, line by line
The first column describes Neve as owners actually run it: the free theme, the Neve Pro plugin, a builder or block pack, WooCommerce where there is a store, and the plugins that patch the gaps. The second is a custom Next.js build. The third adds Athena CMS, the editor we ship with every site.
| Neve + plugins | Next.js build | Next.js + Athena CMS | |
|---|---|---|---|
| Performance | Light core; weight arrives with Neve Pro modules, the builder and starter-site content | Each route ships only the components it renders | Identical front end; the editor adds no visitor-facing code |
| Core Web Vitals | Reachable on a lean build; Pro's Lazy Rendering helps until a plugin undoes it | Image dimensions, font loading and layout fixed in code before launch | Same, with Argus flagging a page that slips |
| Hosting requirements | PHP 7.0 and WordPress 5.5 minimum; nearly any shared host qualifies | Node build, then CDN or serverless hosting | Same, plus Athena's content store |
| Security | Small theme footprint; exposure sits in Pro, Otter, Woo extras and wp-admin | No public login page or plugin endpoints to probe | Same, with Aegis scanning daily for backdoors |
| Plugin dependency | Moderate: Neve Pro, a builder or Otter, cache, SEO, forms | Pinned packages, tested in a build, nothing installed live | None at runtime; agents handle the chores |
| Maintenance | Theme, Neve Pro, Otter and each plugin update on separate calendars | A developer bumps dependencies and runs the build | Same, with agents checking links, forms and certificates |
| Updates | Frequent free releases (4.2.15 on October 1, 2026) applied straight to production | Previewed on a private URL, then deployed | Code previewed; content publishes without a deploy |
| SEO | Clean theme markup; titles, sitemaps and redirects come from an SEO plugin | Metadata, sitemaps and redirects written into the routes | Same, with Iris drafting titles and social cards |
| Schema | Handed to the SEO plugin; page-type schema needs custom code | Typed structured data per template | Same, regenerated as content changes |
| Page speed | Vendor cites 28KB and 0.6s on a default install; real pages weigh more | Static pages from a CDN edge | Same |
| Mobile performance | Separate mobile header layout; phones still get site-wide plugin scripts | next/image sends phones a phone-sized file | Same, with Picasso keeping images described and sized |
| Custom development | Pro hooks and custom layouts inject content; deeper work needs a child theme | Any feature a React app can hold | Any feature, with fields shaped to your business |
| CMS usability | Customizer for header, footer and colors; content in blocks or a builder | Needs a CMS attached or a developer for edits | Plain fields, live preview, full version history |
| Ecommerce | WooCommerce works free; quick view, wishlist and swatches need Business | Commerce service or custom checkout | Built-in store and Stripe subscription billing |
| Scalability | Fine for small sites; traffic spikes lean on host caching | CDN absorbs spikes on prerendered pages | Same |
| Hosting cost | Lowest of the three on day one | Usage-based; often modest for static sites | Comparable to a plain Next.js site |
| Development cost | Free theme plus $69 to $259 for the first Pro year | Custom build, priced higher up front | Custom build, fixed quote after an audit |
| Long-term maintenance | Pro renews at $139 to $519 a year, plus plugin licenses | Small and predictable | Small, with routine checks automated |
| Content editing | Blocks or builder for pages; settings spread across Customizer panels | Whatever CMS is connected | One editor for pages, posts and products |
| Integrations | A plugin per service, each with its own settings screen | Direct API calls in the codebase | Same, plus agents that act on live data |
| API support | Core WordPress REST API; anything more is a plugin | Route handlers are part of the framework | Same |
| Headless CMS capability | Neve's Customizer and header builder do nothing for a headless front end | Pairs with any headless CMS | Athena is the headless CMS |
Two rows deserve a second look. Hosting cost favors Neve on day one, and that is real money for a new business. Long-term maintenance favors the build, because the Neve column keeps renewing. If you want the mechanics behind the speed rows, read WordPress vs Next.js speed and the section front page for the other themes.
Introductory pricing and the second invoice
As of October 2026, every Neve Pro plan covers unlimited sites. The plans differ by features, not by site count, which is generous for agencies. The first-year prices are promotions, and Themeisle's pricing page says so in plain words: renewals are at full price.
| First year | Renewal | What it adds | |
|---|---|---|---|
| Personal | $69 | $139 | Header and footer extras, custom layouts and hooks, Performance module, content restriction |
| Business | $149 | $299 | 110+ starter sites, WooCommerce Booster, LMS Booster, priority support |
| Agency | $259 | $519 | Otter Blocks Pro, domain mapping, Templates Cloud, white label |
So a store on Business pays $149 now and $299 every year after, before any plugin licenses. There is a 30-day money-back guarantee, which makes trying Pro cheap. The Neve pricing breakdown adds the plugins a finished site tends to need and totals them. None of this makes Neve expensive. It makes Neve a subscription that looks like a purchase.
Where Neve sites come apart
Neve's failure modes are not dramatic. They are the small, maddening kind that come from layers disagreeing. Recent WordPress.org threads show the pattern.
The hamburger that ignores iPhones
In June 2026 a user found the mobile menu unresponsive on iOS Safari and traced it to the SiteGround speed-optimization plugin, not Neve, so the optimizer is the first suspect. Our Neve mobile menu guide walks the checks in order.
Customizer changes that will not publish
An 'expected_array' error blocked saving. Themeisle staff traced it to a malformed theme_mods_neve option and suggested renaming or resetting it. Related symptoms show up as Neve CSS not updating.
Editor styles missing after WordPress 7
One user on Neve 4.2.4 reported broken editor styling after the WordPress 7 update. Staff could not reproduce it, and the thread is unresolved.
Header builder and font surprises
Mobile and secondary menu display issues recur on the forum. When the header misbehaves, start with Neve header builder repairs; when type looks wrong, check Neve fonts not loading.
Notice who caused the first one: a speed plugin installed to make the light theme lighter. That is the WordPress pattern in miniature. The full list of fixes sits under Neve repair, and when an update shifts the layout, start with Neve update broke layout.
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.
Two honest lists for a Neve owner
We build in Next.js, and we still recommend Neve to plenty of people. Here is how we sort them.
When Neve is the better choice
- A five to fifteen page brochure site for a plumber, consultant or clinic, built from a starter site in days
- An owner who wants to move the header around with drag and drop and never open a code editor
- A budget that fits the free theme, or one Pro year with a known renewal
- A small WooCommerce shop where Business-plan swatches and quick view cover every need
- A marketing team that wants hands-on Customizer and block editor control this week
When Next.js is the better choice
- Paid search and local ads drive leads, and every slow landing page wastes budget
- You want hundreds of city or service pages generated from data, not cloned by hand
- The plan includes client logins, quotes, calculators or a booking flow with real logic
- Forms feed a CRM, a scheduler and an accounting system at once
- The site has to stay fast for years without a growing pile of optimizer plugins
If the left column fits, keep Neve lean and let our theme speed team tune it. If you are still shopping themes, Neve vs Astra is the comparison most Neve buyers run first.
Why a Neve site packs up more easily than most
Here Neve's restraint pays a dividend. Because the theme does not lock content into its own builder, pages written in the block editor are ordinary WordPress content. They export cleanly. What does not travel is the presentation: Customizer settings, header builder layouts and anything built with Pro's custom layouts and hooks must be redesigned in the new build. That is design work, not data rescue.
The exception is the builder you chose. A Neve site built in Elementor carries Elementor's data, and that takes more untangling than the theme ever will. Starter-site content also tends to bring demo pages nobody deleted. The Neve to Next.js migration guide covers the order of work, and every move we run keeps your URLs or redirects each old one to its new address.
Simple editing without a yearly Pro renewal
People pick Neve because they want something light that stays out of the way. Athena CMS is built on the same wish, without the renewal cycle. Pages, posts and products are plain fields with a real preview, and every version is kept, so nobody has to fear the Publish button. The content restriction you might buy Neve Personal for becomes password-protected membership areas with login levels and Stripe subscription billing.
The chores plugins nag about are handled by agents. Apollo reads every page and ranks what to fix. Argus watches for broken links, failing forms and slow pages. Ariadne adds internal links. Prometheus finds customer questions your site never answers and drafts the page for your approval. The longer argument is at Athena vs WordPress.
Blogs, service firms and small shops: our call on each
- Personal blog or hobby site: stay on free Neve. It is light, current and costs nothing.
- Local service business with a handful of pages: Neve with a starter site is hard to beat on price. Revisit when ads and lead tracking become the business.
- Small WooCommerce store: Neve Business works. Budget for the $299 renewal and a careful plugin list.
- Agency building many client sites: the unlimited-site Agency plan is good value until clients need features the stack cannot hold.
- Lead-generation or multi-location business: Next.js with Athena. Speed, generated pages and integrations are the product here.
Not sure which line describes you? A free site audit looks at your Neve install and tells you whether tuning or rebuilding is the cheaper road.
Questions people ask before they call
A default Neve install is light, and Themeisle cites 28KB and 0.6 seconds in its own test. A finished Neve site adds Pro modules, a builder and plugins, so it usually weighs more than that. A Next.js build prerenders pages and ships only what each page uses, so it stays fast as the site grows. See the Neve speed guide.
No. As of October 2026 the first-year prices of $69, $149 and $259 are introductory, and Themeisle's pricing page says renewals are at full price: $139, $299 and $519 a year. Every plan covers unlimited sites. A 30-day money-back guarantee applies. The Neve pricing page totals a real site's costs.
Yes, if URLs are kept or redirected and titles, descriptions and content come across. Neve stores page content as normal WordPress content, so the move is easier than from builder-locked themes. Customizer and header settings are redesigned rather than exported. Read the Neve to Next.js guide.
For a small store, yes. The free theme supports WooCommerce, and the Business plan adds quick view, wishlist, comparison and variation swatches. Larger catalogs and custom checkout logic push past what a theme plus extensions handles comfortably. If your shop pages break, start with Neve WooCommerce layout broken.
Pro features live in the Neve Pro plugin rather than the free theme, so the free theme keeps working either way. How Themeisle handles updates and support after expiry is set by its license terms, so check your account before the renewal date. If activation itself fails, see Neve Pro license not activating.
Keep reading
- Theme vs frameworkAstra vs Next.js: A Light Theme, a Heavy Stack and a Custom BuildAstra vs Next.js, row by row: the 2026 AI bundles, the 3-site Pro cap, Elementor and Spectra, real failure modes, and when Astra is still the smart buy.
- New owner, old questionKadence vs Next.js: A Block-First Theme Under New Owners, Against Custom CodeKadence vs Next.js after the Liquid Web shake-up: Kadence Blocks, the new $99 to $499 plans, known issues, and which businesses should stay or move.
- WordPress at its leanestGeneratePress vs Next.js: The Fairest Fight WordPress Can OfferGeneratePress vs Next.js, argued fairly: a sub-10kb theme, a $59 license for 500 sites, the coming template engine, and where a custom build still wins.
- A Customizer theme, weighedBlocksy vs Next.js: A Great Free Theme Against a Site With No Plugins at AllBlocksy vs Next.js compared on 22 rows: the free header builder, Companion and Pro, lifetime licenses, the 2.1.5x regressions and when to stay put.
- The Elementor stack, weighedHello Elementor vs Next.js: The Empty Theme and the Builder That Fills ItHello Elementor vs Next.js on 22 rows: the 6KB vs 30KB claims, Theme Builder dependency, Elementor's real weight, and when the builder is the right call.
- The developer's builderBricks Builder vs Next.js: The Best Case for Staying on WordPress, TestedBricks Builder vs Next.js on 22 rows: clean output, no jQuery, the $599 lifetime plan, 2.4 AI editing and its regressions, and where Next.js still wins.
- Everything in WordPress vs Next.jsSee the section
Get a straight answer on your Neve site
Tell us what the site does and what is bugging you. We will look at the install and say whether to tune Neve, rebuild in Next.js, or leave it alone.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.