Work

Linked Text Frames for Figma

A native concept for InDesign style text threading in Figma, with a working plugin as proof.

Role
Solo (research, design, prototype, plugin build)
Timeline
October to November 2026
Scope
Product design, interaction design, desk research, prototyping, plugin development
Tools
Figma, Figma Plugin API, TypeScript

Independent student concept. Not affiliated with, endorsed by, or sponsored by Figma.

Overview

Figma has no way to flow one story across text boxes.

InDesign already does. Text that does not fit in one frame flows into the next, and the story reflows when the copy changes. In Figma, every text box stands alone.

Blue banner labeled The brief with the question: How might we let long text flow across boxes in Figma, so editorial layouts can stay in one collaborative tool?
A Figma style editor where text is linked across three magazine columns, reflows on edit, and survives a deleted column.
The concept in about a minute.

My role

I did this solo, from October to November 2026: desk research, principles, three directions, an 8 screen UI3 concept with a Smart Animate prototype, and a working Figma plugin that proves the behavior on a real magazine spread.

Problem

Every text box in Figma is an island

In InDesign, text that does not fit in one frame flows into the next linked frame. Edit a paragraph, resize a column, or delete a frame, and the story reflows. In Figma, every text box stands alone. Multi column layouts, magazine spreads, reports, and text heavy slides all mean splitting copy by hand and redoing it every time the copy changes.

Light gray banner labeled The problem with the line Every text box in Figma is an island, framed by scattered, unlinked text box shapes in blue, mint, red, white, and black, one of them showing a red overflow plus.

People have been asking for five years

The main Figma forum request, "Link textboxes in Figma", was opened in April 2021. On November 10, 2026 it showed 55 replies and 12,508 views. Newer requests keep appearing, including one from a Figma Slides user in December 2025.

Screenshot of the Figma forum thread titled Link textboxes in Figma, showing 55 replies and 12508 views and the first replies.
The public "Link textboxes in Figma" thread on the Figma forum, captured November 10, 2026.

"I found this thread while trying to figure out if I should convince a collaborator to move from InDesign to Figma. If text wrapping between text boxes is not possible, we'll be sticking with InDesign."

Nick_DeMaison, Figma forum

"Just keeping this alive. I'd rather have simple and extremely useful things like this than AI, which is blocked in my company anyway..."

Bas_Poppink1, Figma forum

The opportunity

What if text in Figma could flow from one box to the next, the way it has in publishing tools for years?

Mint banner labeled The opportunity with the question What if text in Figma could flow from one box to the next, the way it has in publishing tools for years? Three numbered text boxes climb toward the corner, joined by blue thread lines.

Research

Desk research

I read every forum request end to end, studied how InDesign, Affinity Publisher, and QuarkXPress thread text, and checked whether any browser based design tool does it today.

  • InDesign gives every frame an in port and an out port. A red plus in the out port means overset text.
  • Affinity Publisher uses flow triangles on the frame corners and can show the text flow as lines.
  • QuarkXPress uses a separate linking tool and shows the chain as arrows.
  • Canva's help center lists "Text won't automatically flow across multiple text boxes" as a limitation. Penpot's team confirmed in May 2026 that it cannot run text from one element to another.
Diagram titled What people do today with three linked squares. Copy split by hand, redone on every edit. Overflow is easy to miss, fixed boxes do not pass it on. Work stays in InDesign, for ebooks, reports, and layouts.
What people do today: split copy by hand, miss overflow, or keep the work in InDesign.

Competitive analysis

Comparison table of InDesign, Affinity Publisher, QuarkXPress, Canva, Penpot, Framer, Figma today, and this concept across linked text boxes, overflow indicator, visible thread, and reflow on edit.
Publishing tools thread text. Browser design tools do not. Checked November 2026 from each product's docs or community answers.

Plugins exist, including the community plugin Text Threading (September 2026) and my own prototype. That shows demand, but a plugin cannot draw ports in Figma's own interface or reflow live while you type. That gap is the case for a native feature.

Persona hypotheses

Three persona cards, each tagged Hypothesis, not validated: the editorial designer, the slide builder, and the product designer with long copy.
Three hypotheses drawn from public forum posts. Not validated.

These are assumptions, not findings. I have not run interviews yet.

Interviews planned

Next, I plan to interview 5 to 6 designers who do editorial or long text work, and run a short unmoderated test on the prototype. The screener, discussion guide, and test plan are ready.

Principles

What makes threading feel like it belongs in Figma?

Tile labeled Feel native. A selected mint text box with a blue out port sits beside a panel whose Text flow control reads Linked, 1 of 3.
Feel native. Threading should look like it shipped with UI3.
Tile labeled Never lose a word. A text box with a red overflow plus, and a dark toast reading Box deleted. Text kept. Undo.
Never lose a word. Overflow is always visible, and deleting a box keeps its text.
Tile labeled Show the thread when it matters. Three numbered text boxes step down the tile, joined by blue thread lines between their ports.
Show the thread when it matters. Ports and lines appear on selection.

Explorations

How should you create and see a thread?

I compared three directions side by side on one decision board.

Decision board with three cards. Direction A, Port and link, marked Recommended for v1. Direction B, Flow Auto Layout property. Direction C, Story object.
Direction A leads v1. B is a complementary Auto Layout shortcut. C is a later power-user story object.

Direction A: Port and link (recommended for v1)

Canvas-first connectors. Every text frame gets in and out ports, it works across freeform pages, and it is the best match to what people ask for when they mention InDesign.

Direction B: Flow Auto Layout property

A parent Flow property that runs text across its children. Great inside structured layouts, and complementary to ports rather than a replacement.

Direction C: Story object

A named story in the Layers panel. A power-user story object that is strong for long documents, planned as a later milestone after ports.

Why ports and link?

Ports work anywhere on the canvas, not only inside an Auto Layout parent, and they match the model people already know from InDesign and Affinity. B and C stay on the roadmap: B as a shortcut for structured layouts, C for long documents once ports exist.

Two labels joined by a plus: Works anywhere on the canvas, plus A model people already know. Around them are scattered text boxes, ports, a blue thread line, a red overflow plus, and a cursor.

Direction A in wireframes

Before going high fidelity, I wireframed Direction A through 13 states, including edge cases like multiplayer, page breaks, keyboard only linking, and cycles.

All Direction A wireframes on one board.
Wireframe of a single text frame with small in and out ports on its edges.
Ports appear on hover and selection.
Wireframe of a loaded cursor linking one text frame to an empty frame beside it.
Click the out port, then the next frame.
Wireframe of linked text frames placed inside an Auto Layout container.
Where A meets B: linked frames inside an Auto Layout parent.

Solution

Text flow: thread text the way Figma would

Eight screens at 1440 x 900, drawn to look like Figma UI3 on a real "Wander" magazine Lisbon spread, linked with Smart Animate.

The right panel Typography section with a Text flow control below Alignment, and the selected column's out port highlighting.
Find it where text lives. Select a fixed size text box and a new Text flow control appears in Typography. Its Link button highlights the out port.
Close up of the Typography section with a Text flow row showing link status, plus Previous frame and Next frame fields.
The Text flow control sits under Alignment, with the previous and next frame listed below.
Selecting the first column of the Lisbon spread brings up the Text flow control.
Select a column and Text flow shows what that box can do.
A text column with a red plus on its out port, showing overset text.
Overflow is never hidden. A red plus marks text that does not fit.
Clicking the out port on column one, then column two, and the text continuing across columns with a thread line.
Click the out port, click the next box, and the story flows across.
The Layers panel listing the linked columns as one thread, with each column highlighting on the canvas.
The thread is readable in the Layers panel too.
A collaborator cursor edits a column and the text in the following columns shifts to fit.
Edit anywhere, even with a collaborator, and the rest of the story reflows live.
Deleting the middle column, a toast confirming the text was kept, and Undo restoring the column.
Delete a linked box and its text stays in the story. Undo is one click away.

Smaller decisions

What happens when the thread changes?

Diagram titled When the thread changes with four squares. Delete a linked box: text kept, Undo. Resize a box: reflows as you drag. Mixed styles: every run keeps its style. Link back into the story: cycles blocked.

Deleting a linked box

First pass: a confirm dialog on every delete, asking whether to stitch the neighbors together or park the text as unlinked overflow.

Final: delete right away, keep the text in the story, and show a toast with Undo.

Why: a dialog interrupts every delete and asks a question most people cannot answer yet. Undo protects against the rare mistake at no cost.

Wireframe of three linked frames with the middle one selected and a dialog titled Delete middle frame with Stitch neighbors, Park text, and Cancel.
First pass. A dialog asking whether to stitch neighbors or park text.
Deleting the middle column, a toast confirming the text was kept, and Undo restoring the column.
Final. The text stays in the story, a toast confirms it, and Undo brings the box back.

Resizing a box

Alternative: reflow only when you press a Reflow button, which is how my plugin works today.

Final: the thread reflows as you drag. Shorten column 1 and its lines carry into columns 2 and 3. When there is no room left, column 3 shows the red plus.

Dragging the bottom handle of the first column up, the text shifting into the second and third columns, and a red plus appearing on the third column.
Drag column 1 shorter and its lines carry into columns 2 and 3 until column 3 overflows with a red plus.
The first column selected with its bottom resize handle grabbed.
Grab column 1's bottom handle.
The first column shorter, with its last lines now at the top of the second column.
Lines carry into columns 2 and 3.
The third column full, with a red plus on its out port.
Column 3 overflows with a red plus.

Mixed styles

Alternative: apply one style to the whole story. My first plugin build did this, and the drop cap's color and leading spread onto all the body text.

Final: every run keeps its own style. After an edit, an italic run, an Anton drop cap, and a bold run move from column 1 to column 2 intact, and column 3 overflows.

Editing the first column while styled text, including an italic phrase, a large drop cap, and a bold phrase, reflows into the second column unchanged, and the third column shows a red plus.
After an edit, the italic run, drop cap, and bold run move from column 1 to column 2 with their styles intact.
The first column with an italic phrase, a drop cap, and a bold phrase.
Styled runs in column 1.
The same italic, drop cap, and bold runs now at the top of the second column.
After the edit, the same runs sit in column 2, styles intact.

Linking back into the same story

Decision: block it. Trying to link frame 3 back into frame 1 shows an inline message and a red invalid target, so a story can never loop.

Wireframe of three linked frames with frame 1 outlined in red and the message Cannot create a cycle. Frame 1 is already earlier in this story.
Cycles are blocked with a clear reason.

Plugin as proof

A concept can fake anything, so I built it

I wrote a working development plugin, Linked Text Frames (Prototype), in TypeScript on the Figma Plugin API and tested it on the real Wander spread. On November 10, 2026, link, reflow, auto reflow, and delete all worked in Figma.

View the plugin on GitHub

The Linked Text Frames plugin panel with order options, a Link button, and Auto-reflow and Show overlay checkboxes.
Open the plugin from Plugins, Development. Choose the order, link, and turn on auto reflow or the overlay.
Three magazine columns selected, the Link button clicked, a toast reading Linked 3 frames and reflowed, and thread lines between columns.
Select three columns and link them. The story reflows and thread lines appear.
Typing in the first column, then the plugin reporting Auto-reflow complete as text shifts across columns.
Edit column one. About a second after typing stops, the story reflows.
The middle column deleted, the thread line rerouting, and a red overset marker on the last column.
Delete the middle frame. The thread reroutes and a red marker flags overset text.
A new text frame drawn on the spread, filling with the remaining text as the overset marker clears.
Draw a new frame and the overset text flows into it.

How it works

  • The story and its order are stored in shared plugin data, so a thread survives closing the file.
  • A binary search with one off canvas probe finds how much text fits each box. The probe is always removed.
  • Splits never land inside a word and avoid an orphan word at the top of a column.
  • Every run keeps its font, size, line height, letter spacing, case, and fill.
  • Auto reflow waits 1.2 seconds after the last edit, ignores its own writes, and never overwrites your typing.

What building it taught me

  • Auto reflow looped on its own writes at first. Recognizing its own edits by content fixed it.
  • Deleting a frame used to lose its text. Now every reflow records what each frame holds, so delete and Undo are safe.
  • A plugin cannot add ports to Figma's interface or reflow while you type on the canvas. That is the case for building it natively.

Outcome

A native concept and a plugin that proves it

The result is an 8 screen UI3 concept with a Smart Animate prototype, 9 prototype clips, and a working plugin tested on a real magazine spread. This has not shipped and has not been tested with users yet, so there are no usage numbers. Next, I will run the interviews and the unmoderated test, and check every estimated UI3 value against the official kit.

The Wander magazine Lisbon spread on a mint background, its story flowing across three numbered, linked columns, with a Text flow panel reading Linked, 1 of 3, Previous frame None, Next frame Lisbon / Col 2.
The concept: the Wander Lisbon spread threaded across three columns, with Text flow showing Linked, 1 of 3.
The Linked Text Frames prototype plugin panel over the Wander Lisbon spread in Figma, with the story flowing across three columns marked 1, 2, and 3 and joined by thread lines.
The plugin: the same spread in Figma, linked across three columns by my working plugin.

Reflection

Building it changed the design.

Delete, drop caps, and typing during a reflow only showed up once real text moved through real boxes.

A small feature still has to respect the whole system.

Threading had to work with Undo, the Layers panel, collaborators, and the way people already think about text.

Independent student concept by Immanuel Mensah. Not affiliated with, endorsed by, or sponsored by Figma. Figma and UI3 belong to Figma.

Magazine photos from Wikimedia Commons (CC BY or public domain), credited on the pages: Paxson Woelber (cover), Tiomax80 (contents), Dale Cruse (Lisbon rooftops), Christine Zenino (tram), and thumbnails by Ben and Gab, Joshua Tree NP, Sanshiro Kubota, Don Ramey Logan, procsilas, Winky, and Pierre Selim Huard.

Forum quotes are from public posts on forum.figma.com, credited by username.