Check out Vizy 4

Verbb Team Verbb Team Oct 2026 5 min read

Blog vizy 4

Vizy has always been about mixing rich text with blocks of regular Craft fields in one editor, and storing the lot as structured JSON instead of a blob of HTML. Vizy 4 keeps that idea and rebuilds just about everything around it, with a new editor on Tiptap 3, editor configs you can share across fields and, the one we're most excited about, layouts.

Sometimes content needs two columns, and it shouldn't take an entire page builder to get them.

We'll get to layouts below. First, a heads-up, because this is a major release with a new document model, GraphQL schema and extension APIs, and it needs Craft 5.9 or later. If you're upgrading, start with the upgrade guide and try the whole upgrade on a copy of your site before going anywhere near production.

A Rebuilt Editor on Tiptap 3

Vizy has been built on Tiptap (opens new window) since we launched it in 2021, and Vizy 4 moves to Tiptap 3. For authors, writing, formatting and adding blocks should feel familiar, but toolbars, menus, dialogs, block controls and keyboard behaviour now act the same way across the whole editor.

Vizy4 editor
Same idea, with a lot more polish around the edges.

Behind the scenes, we've moved away from Vue and rebuilt the interface with web components and Plugin Kit. Most authors will never need to think about that, but it gives us a much cleaner foundation, and it's what layouts, footnotes and the rest of this release are built on.

Editor Configs You Can Reuse

Vizy used to have you set up its editor with a chunk of JSON on each field. Vizy 4 replaces that with named Editor Configs that you build visually under Settings → Vizy → Editor Configs and reuse on any field that needs the same set of tools. You can create one from a field's settings too, without losing your place.

Arrange the toolbar, dropdowns, Bubble Menu and block insertion controls, and swap control icons for your own SVGs if your editors know a different symbol. For the advanced folks, you can also decide which content is allowed in the editor at all.

Vizy4 editor config
Give every field the tools it needs, and leave the rest in the shed.

Configs are stored in Craft's project config, or as JSON files in config/vizy/ when you'd rather keep them in your repository. The Editor Config docs cover both.

Block Types Shared Between Fields

Until now, every Block Type belonged to a single Vizy field. That kept things simple behind the scenes, but if the same Callout block turned up in five fields, you built it five times and kept all five in step.

In Vizy 4, Block Types are global, stored in project config. Create a Callout or a Gallery once, with its field layout, icon, colour, preview image and Twig template, then let any Vizy field use it. Each field picks which Block Types it allows and how they're grouped, so an Article Body might offer all the editorial and media blocks while a Sidebar keeps the choice deliberately small.

Authors can add a block from the toolbar, the + in the gutter or by typing /, and pick from a searchable list or a grid of previews. Each field decides which views are available and which one opens first.

Vizy4 block picker list
Find the right block by name, group, icon or preview instead of playing component roulette.

Block Types can use Craft's conditions too, so a block can be offered only when the entry matches a rule, and fields or tabs inside a block can show and hide as an author fills it in. Collapsed blocks show a short summary of what's inside, and their content can appear in Craft's element card previews.

Vizy4 block picker grid
Add a preview image to each Block Type and the grid view does the rest.

Layouts and Columns

Vizy 4 adds Layout and Column nodes right inside the editor. Choose a preset, drop rich text and blocks into the columns, then resize, reorder or wrap them as the content takes shape.

Because a layout is part of the document, an author can put together a comparison or an image-and-copy section without breaking the article into separate blocks around it. Layouts use a 12-column structure and record where their columns should stack. Your CSS decides what that breakpoint looks like, using the .vizy-layout and .vizy-column classes.

Vizy4 layout
Two columns, no page builder required.

The Layouts documentation has the authoring controls and a full front-end styling example.

Footnotes and Other Writing Tools

There are plenty of new writing tools, all opt-in through Editor Configs:

  • Task lists and collapsible Details sections
  • Find and Replace, with whole-word, case-sensitive and regular-expression matching (for the regex wizards)
  • Ruby text, emoji and syntax highlighting
  • Font family, font size, text colour, highlight and line height controls
  • Character counts, placeholders and typographic replacements
Vizy4 authoring tools
Task lists for all those todo lists you need to make.

Footnotes are built in too. Back in the Redactor days, we made a Footnotes plugin, and now they're part of Vizy, with paired references, editable definitions, automatic numbering and keyboard navigation. If your content already uses our Footnotes markup, Vizy 4 can migrate it.

Vizy4 footnotes
Footnotes, numbered for you.

Pasting from Word has always been a bit of a lucky dip, so that's had some attention too, along with Google Docs. Vizy keeps the formatting the field allows and warns you when something can't come across. Pasted links are checked for unsafe schemes, and media embeds fall back to a plain link when a player isn't supported.

Vizy4 find replace
Typo hunters, rejoice.

The Editor Capabilities reference lists everything you can turn on.

Moving From CKEditor or Redactor

If you're using CKEditor or Redactor fields today, you're probably wondering how much of your content can be moved across. Vizy 4 has tools for exactly that. A control panel wizard (or console command) converts CKEditor, Redactor and Plain Text fields to Vizy, shows you a preview of the conversion first, keeps recovery data, and generates a migration for deploying the change. Feed Me imports report anything that couldn't be converted, and can insist on a lossless conversion. Read Migrating CKEditor and Redactor Fields and Importing with Feed Me before you start.

GraphQL and Extensions

Headless projects get a new structural GraphQL API for documents, nodes, marks, layouts and blocks. Ask for rendered HTML when Craft should own the output, or typed nodes when you'd rather build the output in your front end.

For extensions, Vizy 4 swaps mounting Vue components or reaching into the editor's DOM for supported PHP and JavaScript APIs. Register your own Tiptap nodes, marks, behaviours, controls, dropdowns, link options and rendering, and your extension no longer depends on how the editor happens to be built. Existing extensions will need moving across, and the Extending Vizy guide has complete module examples.


The upgrade guide covers the breaking changes, and the release history (opens new window) has the full detail. Vizy 4 (opens new window) is available today for Craft 5.9 and later. Have fun!