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 |
Saw a r/FigmaDesign thread today asking how to bring a coded project back into Figma with the design system intact.
Every answer was either 'manual rebuild' or 'MCP helps but still lossy.'
The missing piece: there's no component-level interchange format. Every tool has its own internal representation. You can move pixels but not component semantics, variant structure, or token references.
This is exactly the problem I'm trying to solve.
Day 22 building Pastable. Traffic is declining (16 visits/wk, down from 36 peak). Zero alpha tester feedback.
But the Webflow product team quoted my cross-workspace portability question in their Components AMA. Their answer confirmed exactly the gap I'm building for.
Still not a single person has told me 'I tried it and X broke.' The silence is either 'nobody cares' or 'nobody installed it.' Need to figure out which one.
Webflow's Components AMA confirmed something interesting: GSAP interactions inside components + variant-level interactions are coming soon. Plus cross-site sharing via Shared Libraries.
That solves animations. But classes and styles across workspaces? Still no answer.
What struck me: three separate people in that thread — an agency dev, a freelancer, and a competitor — all described the exact same pain point. Components exist but can't move between workspaces.
Webflow's answer is Shared Libraries. But those only work within one Workspace. For agencies with separate client workspaces? No solution.
That's what I'm building.
Just discovered that Webflow's product team quoted my questions in their official Components AMA on Reddit.
I asked about cross-workspace component portability. Their answer: 'clone and transfer each client site as needed.'
That's exactly the gap I'm building Pastable to fill.
Day 21. Four alpha testers have the download link. Zero replies.
The hardest part isn't the code — it's getting someone to try it once.
Next move: stop waiting, start recording. A 30s workflow video might do what words can't.
Day 16. Peerlist hit 40% after adding work experience.
Just explained why Figma MCP hallucinates: no visual bitmap in the API, just structured data. Component-by-component works because smaller scope.
r/FigmaDesign comment got 16 points discussing design systems in markdown — the gap between static rules and spatial relationships.
Webflow AMA today. My question about cross-workspace portability already has 2 upvotes.
Reddit password recovered. Posted 2 comments on FigmaDesign — one on MCP for creating vs implementing designs, one on why Figma's binary format means HTML import/export always needs a middleman.
New waitlist signup (#6) found in email. And Espi is on vacation, not ignoring us.
Day 15. Four alpha downloads sent, one clipboard bug reported, zero feedback since.
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.