00:00
/
00:00
Figma plugin — built by Tribal House
Figma keeps a history of your whole file. Manifest keeps a history of the parts you ship inside it — commit a frame, cut a release, publish a changelog.
Pick a frame, component, or page, write a message, and commit it to a named release. Every commit saves a snapshot and a preview — so a release still shows what it held months later.
Committing
Checkout / Payment step
Message
Published to the web
Roll a release into a changelog and publish it to a shareable page with its own link and RSS feed. No Figma seat required to read it.
Jul 01, 2026
Published with Manifest — release notes for the Acme design system.
Release history
Tighten spacing, add Apple Pay row
New order summary card
Full history →
In Dev Mode, click a layer and Manifest shows every release it belonged to — whether it’s ready for handoff, the designer’s notes, and linked reviews. The latest handoff-ready commit is front and center. No more digging through comments.
On the same rails as code
GitHub 
Linear 
Slack GitHubRelease v1.2.0 created
Slack · #designManifest — v1.2.0 shipped
Issue ACM-214 updated
Power tools
Scan every font in scope and remap it to a new family — styles matched automatically by weight and italic.
Find raw, style-bound, and variable-bound colors, then bulk-replace them with a color, paint style, or variable.
Scan for rogue colors, unstyled text, and detached instances — free — and bulk-fix the confident ones.
Also in Manifest
Manifest lays out a “Release Index” page inside the Figma file — one section per release, cards grouped New, Updated, and Handoff-ready — so the team sees what shipped without opening the plugin.
Commit a component out of one file and land it in another — into a published library or a client file — on a named release.
Runs on Figma Starter through Enterprise. No API keys, no org setup, no seat required to read a published changelog.
How it works
Select what you shipped — a frame, component, or page — and commit it with a message. Manifest snapshots it with a preview.
Group commits into a named, semantic release. It rolls up into a changelog and a board inside your file.
Push the changelog to a public page with a link and RSS feed, and hand off to developers in Dev Mode.
Questions
Manifest is a Figma plugin that adds version control to Figma. You commit frames, components, and pages into named, semantic releases (like v1.2), and Manifest builds changelogs, a release board inside your file, and Dev Mode handoff from those commits.
Figma’s version history is one undifferentiated timeline of the whole file. Manifest adds a deliberate release layer on top — so “what shipped in v1.2” has a real answer, and each release keeps a snapshot and preview of exactly what it contained.
Yes. Manifest runs on every Figma plan, from Starter through Enterprise. On Starter it consolidates the release board onto a single page instead of many.
Yes. Developers open Dev Mode, click any layer, and see every release it belonged to, whether it’s handoff-ready, and the designer’s notes. Anyone can also read a published changelog on the web — no Figma seat required.
GitHub (real commits, tagged releases, and PRs), Linear and Jira (link and update issues on release), Slack (release notifications), and Chromatic/CI (build status next to the matching commit).
Yes. Manifest is published on the Figma Community and free to install — open the listing, click Open in Figma, and it runs in any file you have edit access to.
Manifest is live on the Figma Community. Install it and cut your first release today.
A Tribal House product