NocoDB 2026.05.1 released on 18-05-2026
NocoDB 2026.05.1 is out now. It delivers personal Bookmarks for quick access, a Smart Text field that turns long-text cells into full NocoDocs editors, Mermaid diagrams in NocoDocs, and a larger, smoother Timeline for both short- and multi-year planning — useful for quicker navigation and richer in-record content.
See the release notes on GitHub and the NocoDB documentation for full details and installation instructions.
What’s in this release
- Bookmarks — personal, private shortcuts in a dock flyout with folders, drag-to-reorder, search, automatic cleanup when targets are deleted or access is revoked, and synced renames/colour changes. (Cloud: Plus+; Self-hosted: Business+)
- Smart Text Field — a Long text variant that opens a NocoDocs-powered editor per cell (rich formatting, lists, tables, code blocks, math, callouts, file attachments and embeds), compact markdown previews in the grid, resizable side-panel editor with fullscreen, row navigation and export to Markdown/HTML/PDF. Requires an internal NocoDB-managed PostgreSQL base. (Cloud: all plans; Self-hosted: Business+)
- Mermaid Diagrams in NocoDocs — render Mermaid code blocks as SVG inside NocoDocs (flowcharts, sequence, ER, Gantt and other diagram types), view as code/split/diagram, download SVG, and preserve diagrams in HTML/PDF exports or keep source in Markdown. (Available on all plans, including Community Edition)
Upgrade notes
- Breaking change for self-hosting: NC_PUBLIC_URL has been renamed to NC_SITE_URL and is now mandatory. Set NC_SITE_URL to your instance’s public URL during the upgrade to avoid broken shared links, OAuth redirects and email links.
- Self-hosted Business licences can be purchased via Cloud → Account → Self-Hosted Licenses and activated by pasting the key into Admin → License; activation requires a self-hosted instance on PostgreSQL (SQLite/MySQL deployments must migrate before activating paid features).
Share your experience and any issues you hit — comment, file feedback or report bugs on the project’s GitHub so the team can follow up.
