Differences between the legacy editor and Form Studio

Last updated: August 17, 2026

Form Studio is the new form editor. Your forms didn't change — most of the controls you already know just live somewhere else and a few things are new!

What's covered

This lists what moved, what's new, and what's no longer in the editor.

Your forms, fields, paths, rules, translations and PDF mappings are untouched. This is only about where you edit them.

Where things moved

What

In the legacy editor

In Form Studio

Field settings

A docked panel on the right, with Close and Save at the bottom. Type was read-only.

The gear on a field opens the field settings popover — BASICS, then OPTIONS, then Visibility, then Delete and Save. Visibility rules live here too.

Page settings

A panel on the right holding the page name, the assignee, and the Quiz and Require authentication add-ons.

The gear in the page bar opens the Page settings dialog, with the same controls and add-ons.

Translations

A separate page with a table of languages, one row each.

The Translations tab, with an Add language box and a card per language badged Visible to candidates.

PDF mapping

A separate page split across Edit PDF and Field Mappings sub-tabs, each saved on its own.

The PDF tab. FORM FIELDS and PDF FIELD stack on the left, and one Save writes the PDF and its mappings together.

Auto-annotating a PDF

An Auto Annotate button on the PDF toolbar, behind a confirmation dialog.

Ask Onboarded AI, or use the Auto-annotate the PDF chip on the PDF tab.

Generating mappings with AI

An AI Generate Mappings button in the Field Mappings action bar.

Ask Onboarded AI, or use the Auto-map fields chip.

Assets

An Assets panel at the bottom of the left panel, opened with Open.

An icon button in the PAGES panel header. Same gallery, same Copy URL and Copy HTML actions.

Raw YAML

A separate page, where saving opened an old-versus-new diff to review first.

Edit YAML (advanced) in the header, which validates as you type.

Auto-annotate no longer asks you to confirm. In the legacy editor it sat behind a dialog warning that it would clear the annotations already on your PDF. In Form Studio you ask Onboarded AI for it and it runs as soon as you accept. It still replaces what's there, so confirm you're on the PDF you mean before you ask.

What's new in Form Studio

What

What it does

The Onboarded AI panel

A blue AI pill in the bottom-right corner expands into a panel headed ONBOARDED AI. It holds the chat, the suggestions and undo/redo, and follows you across all three tabs. It starts collapsed.

A chat that answers and edits

Ask what the form collects and you get an answer. Ask for a change and you get proposed edits, each with a before-and-after and its own Accept or Ignore. Find on canvas jumps to the field a proposal touches.

Suggestions for this form

Checks run against your form as you edit and surface small fixes in the panel. Check now re-runs them, and Suggestion settings turns individual checks off.

Let AI make changes

A switch at the bottom of the panel, off by default. On, the assistant applies its own edits instead of waiting for you. Removing a field still needs your approval either way.

Undo and redo

In the panel header, covering your edits and the assistant's in one history. Undoing a deleted repeatable group brings the group back but not the fields inside it.

One page, three tabs

Canvas, PDF and Translations are tabs on one screen rather than separate pages, so your selection and scroll position survive the switch.

Publish in the header

Publishing a draft no longer means leaving for version history. Publish opens the same Deploy Form Version dialog, release notes and all.

Changing a field's type in place

Type is a select in the field settings popover, so a field can convert without being deleted and rebuilt. It covers text, email, phone, number, currency and tax_id only, and it clears that type's options while keeping the path, the label and any rules.

Limits on what the assistant builds

Onboarded AI creates 14 field types. Content blocks, review tables, timers, QR codes, repeatable groups, file upload, file view, formula and integration fields are added by hand from Add Field — the form supports them, the assistant just doesn't build them.

What's no longer in the editor

What

What to do instead

The PDF mapping repair tools — Debug, the N Error(s) button and its Delete errors action

These cleared mappings left pointing at annotations that had been deleted. The PDF tab doesn't carry them, so a form with orphaned mappings can't be repaired from the editor — contact support with the form name and version.

The old-versus-new diff when saving YAML

Edit YAML (advanced) validates as you type and replaces the whole form when you save, with no diff to review first. Copy the YAML somewhere safe before you edit it.

The unsaved-changes prompt between the form and its PDF

Because the tabs are one page now, moving from PDF back to Canvas doesn't warn you about unsaved box edits. Hit Save on the PDF tab before you switch.

Related