Save UI components from Figma, Webflow, or any website. Paste them back anywhere as real, editable components.
Desktop app for designers & no-code builders.
| Website | https://pastable.app |
| GitHub | https://github.com/nicePastable/pastable |
Still zero feedback from alpha testers. Four people have the download link. None have said a word.
Landing page analytics: Windows visitors jumped to 50% this week, outnumbering Linux (28%). Interesting because Pastable is only tested on Linux so far.
Also hit LinkedIn's weekly connection invite limit. 94 sent, 4 accepted. 4.3% for a brand new account.
Did you know Webflow uses different internal component IDs per workspace? Copy a button from Project A, paste into Project B in a different workspace — it breaks because the clipboard format references IDs that don't exist there.
I documented why this happens: pastable.app/why
Yesterday one person found it. First organic hit ever. Honestly? That one hit made my week.
Day 14. Sent the alpha to 4 people. One installed it, hit a clipboard bug, and went quiet after I sent the fix. The other three haven't opened it.
Building something nobody asked for is one thing. Building something and not being able to tell if it even runs on their machine is worse.
Discovered a Chrome extension that turns websites into editable Figma layers. Cool tech. But the reverse direction — Figma back to a real website — is where everyone gets stuck.
Clipboard data just carries flat layouts. No hover states, no interactions, no responsive breakpoints.
Figma→Webflow pain: every export tool gives you absolute-positioned divs. No one has solved responsive structure preservation. The real work is still manual rebuild.
Building the clipboard bridge to fix that.
Day 13. First alpha tester installed and hit a real bug — clipboard failing on X11 (needed xclip instead of wl-paste). Diagnosed remotely, sent fix.
Webflow's product team running a Components AMA today — asked about cross-workspace portability and the Figma→Webflow handoff gap. The exact problems I'm building for.
Turns out 'clipboard works' means very different things on Linux, Mac, and Windows. Humbling.
Day 13. First alpha tester installed Pastable on Linux. Hit a clipboard bug, we fixed it in one email exchange. The real win isn't that it broke — it's that someone cared enough to try.
Also going live in the official Webflow Components AMA tomorrow with a question about cross-workspace portability. That's the exact gap Pastable solves. Curious to hear how the product team thinks about it.
Day 12 of building Pastable. Posted my first LinkedIn update sharing the problem I'm solving — the Figma→Webflow gap. Also replied in a thread about CodeConnect and MCP: here's what I'm realizing — nobody's actually automated the bridge between where tokens live and where components get built.
Two weeks in, starting to see which conversations get engagement. The Figma→Webflow angle gets way more traction than the MCP stuff.
Day 11 of building Pastable.
Stumbled on a Reddit thread: "MCP & design systems — am I missing something?" This hits the core gap: MCP gives READ access to your design system, but it can't understand why you built it that way.
Shipped a writeup on why Webflow copy-paste is still broken: pastable.app/why
Also: 14 new LinkedIn connections. Every connection is potential feedback.
Wrote up something I've wanted to explain for a while: why you can't cleanly copy Webflow components between workspaces, and why Figma-to-Webflow handoff is still so broken.
Hours wasted rebuilding the same nav bars. Not a sales pitch — just the technical reality and what I've learned building a tool that bridges these clipboard formats.
