Gouache

Design collaboration and handoff

Design stays liquid. Handoff stays exact.

One canvas your whole team paints on. Comments stick to the layer they're about, not to a coordinate. Specs come out the other side as real code, not a screenshot and a prayer.

Start a canvas See a handoff

Free for two canvases. No card, no trial clock.

Fig. 01

Untitled (Four Pigments in Water)

Live fluid simulation. Cyan, magenta, yellow and indigo, subtractive, on paper. Move your pointer to paint.

Solving

Studios painting in Gouache

What's different

Feedback that sticks to the work.

Every design tool lets you leave a comment. The comment is usually a pin on a screenshot of a thing that has since moved. Ours doesn't do that.

01

Pins that land on pixels

Drop a pin anywhere. It binds to the layer under it, not to an x and a y. Move the layer, resize the artboard, ship three revisions, and the thread is still on the button it was always about.

Marlow / Home v24

02

Everyone in the same water

Live cursors, live selection, live threads. There's nothing to merge because there was never a second copy. You're both already standing in front of the same sheet.

03

Specs come out as code

Click a layer, get the tokens it actually uses. Real variables from your system, not hex values scraped off a flattened PNG. Copy as CSS, Swift or Compose.

04

Versions you can read

Every save is a frame. Scrub the strip, see exactly what moved, and pull one layer back to Tuesday without reverting the whole file.

05

Rules that catch drift

Set the grid, the type ramp and the token set once. Gouache flags the layer that wandered off before an engineer has to open a bug about it.

The canvas

The file, the thread and the spec are the same place.

No exports. No folder called final with four things in it. The engineer opens the canvas the designer is still painting on and reads the spec off the layer they clicked.

Marlow/Home/Hero v24
Saved 4s ago

Layers

Hero
Eyebrow
Title
CTA
Grid
Washes
Notes

Marlow Studio

Paper &
pigment.

A working archive of things we made wet and let dry in public.

Start a canvas CTA · Pell

Handoff CTA

Fill--ink-900
Text--paper-50
Radius999px
Padding14 / 26
TypeHanken 500 / 15
Tracking-0.005em
/* Hero / CTA, from Marlow tokens */
.cta {
  background: var(--ink-900);
  color: var(--paper-50);
  border-radius: 999px;
  padding: 14px 26px;
  font-family: "Hanken Grotesk";
  font-size: 15px;
  font-weight: 500;
  letter-spacing: -0.005em;
}
Reads live from the layer

One address

The canvas has a URL. That URL is the design, the conversation and the spec. Send it and you're done sending things.

No stale copies

Nothing is exported, so nothing goes out of date. The worst thing that can happen is somebody sees the work in progress.

Reads live

The spec panel isn't a snapshot. It queries the layer. Change the token and the panel changes while you're looking at it.

Pricing

Pick a palette.

Sketch

$0forever

For trying it, and for the small stuff that never becomes big.

  • 2 canvases, unlimited viewers
  • Pins, threads and live cursors
  • 30 days of version history
  • PNG and SVG export
Start free
The one we'd pick

Studio

$18per editor / month

For teams that ship on a clock and argue in public.

  • Everything in Sketch, unlimited canvases
  • Code handoff: CSS, Swift, Compose
  • Two-way token sync with your repo
  • Full history and per-layer rollback
  • Grid and token drift rules
  • Google and Microsoft SSO
Start a canvas

Atelier

Custom

For orgs where the design tool has to answer to a security team.

  • Everything in Studio
  • SAML SSO and SCIM provisioning
  • Audit log and data residency choice
  • 99.9% uptime SLA, 4 hour response
  • A named person who knows your file
Talk to us

Billed yearly or monthly, cancel whenever. Viewers and commenters are always free.

Get your hands wet.

A canvas takes about ten seconds to start. Bring one file, one engineer, and one argument you're tired of having in Slack.

Start a canvas Read the build guide

Free for two canvases. No card, no trial clock.