What Is the Latest ERPNext Version in 2026? Release and Features

I work on ERPNext and Frappe at MithTech, a team of Frappe specialists in Bengaluru, putting the platform in front of manufacturers, distributors, schools and multi-location businesses across India. Version 16 is the biggest jump the platform has made in years, and the questions I hear most are simple: what is current, what changed, and should I move now.

My take: you do not need to move to v16 the week a release ships, but for manufacturers and multi-company groups the planning and reporting changes make it worth scheduling this year.

What is the latest ERPNext version in 2026?

Version 16. Built on Frappe Framework v16, the stable release came on 12 January 2026 after almost two years of work, and point releases have followed roughly every week or two. Version 15 keeps getting maintenance releases for teams still on that line.

The numbering is simple. The major number (16) is the release line; the point releases (v16.x) carry fixes and small improvements. The point number moves fast: v16.50.0 on 6 October 2026 was a "polished" release of v16 that Frappe says has no breaking changes. For planning, the major line matters, not the last digit.

To check your version, open the About dialog from the user menu, or run bench version on the server. That tells you your major line and whether a v15-to-v16 move is ahead of you.

Skimmable summary: Version 16 is the current major line in 2026, on Frappe v16 (v16.50.0 on 6 October 2026), with v15 still maintained.

What are the main features in ERPNext Version 16?

Frappe counts 50+ new ERPNext features in v16 from 600+ contributors. The largest changes are in performance, the interface, manufacturing planning and financial reporting.

The new desk is what most people notice first. v16.50 (October 2026) reorganised it again: an apps desktop, a dock of modules, and a sidebar per module that can be customised for the site or each user. The ERPNext v16 workspace guide walks through the layout.

Skimmable summary: faster performance, a new desk, Chrome PDFs, MRP, inward subcontracting and formula-driven financial reports.

How is Version 16 different from Version 15?

v16 is a full major release, so the differences run deeper than a patch. Performance and the new desk reach every user; MRP and formula-driven financial statements are new capabilities, not refinements.

For most businesses three changes matter. Speed: v16 handles large transaction volumes with less slowdown. Planning: the MRP workflow gives production teams something v15 did not have as standard. Reporting: finance can build formula-driven statements, including multi-company and IFRS-style formats, without exporting to a spreadsheet. On the technical side, v16 needs newer runtimes, so a v15 server must be upgraded before it can run v16.

ERPNext v15 vs v16 compares the two lines area by area, with the runtime details. If you run manufacturing or a multi-company group, the case for moving is strong.

Skimmable summary: v16 differs on performance, MRP, formula-driven reporting and runtimes; v15 stays supported until the end of 2027 (planned).

Is ERPNext still free and open source in 2026?

Yes. ERPNext is free and open source under GPLv3, and Version 16 does not change that. You can download it, self-host it, read the source and modify it with no licence fee.

What you plan for is everything around the software: hosting, implementation, data migration, training and any custom development. That differs from per-user subscription products, where the software itself is the recurring cost. With ERPNext the code is free; the investment is setting it up for how your business runs. How we work with the platform is on the Frappe and ERPNext page.

Skimmable summary: ERPNext v16 stays free and open source under GPLv3; you pay for setup and running, not licences.

Should you upgrade to Version 16 now?

Upgrade when you have a clear reason and a tested path, not because a new version exists. For manufacturers and multi-company groups, MRP and the new financial reports make a strong case to plan the move this year. For a stable single-company setup on v15 with no pressing problem, waiting is fine, as long as you move before v15's planned end of support at the end of 2027.

Whatever you decide, never upgrade production directly. This is the order I follow.

If you rely on custom apps or heavy customisation, get a second pair of eyes before the production cut-over; our support and AMC work covers upgrades.

Skimmable summary: upgrade with a reason and a tested staging path: back up, clone, upgrade runtimes, test workflows, then cut over.

Frequently asked questions