Save UI components from Figma, Webflow, or any website. Paste them back anywhere as real, editable components.
Desktop app for designers & no-code builders.
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.
Week 2 of building Pastable starts. Last week: 50 visits, first Google organic traffic, and 2 people actually accepted a LinkedIn connection from a brand new account with zero followers.
The hardest part of building in public isn't the building. It's being nobody and having to earn every single click.
Sent 10 LinkedIn connection requests today targeting Webflow freelancers. Most without a personalized note because LinkedIn caps those at 5/month on the free tier.
The irony: a networking tool that puts a paywall on saying hello.
Also found a great thread about CodeConnect and component reuse with AI. The real issue: design tools don't tell your codebase a component already exists. So AI rebuilds everything from scratch every time.
@Orhun This is such a cool direction. I'm doing the inverse — taking components OUT of design tools (Figma, Webflow) so they can live anywhere. The real win is when design and code stop being separate islands.
Tried to move a Figma component into a Webflow project today. Obviously nothing transfers. This is the problem Pastable solves — it bridges the clipboard formats between tools. Figma uses a custom binary format (Kiwi), Webflow uses UTF-16LE JSON. I've now decoded all 40 fields in Figma's format. Hover states are not in there at all. They live in component variants on the server. So that's my Saturday. #buildinpublic #figma #webflow
@floberrez The markdown-in-a-folder approach is smart. I've been tempted to build something similar for my own posting workflow -- right now I'm still copy-pasting from a docs file. Starred the repo.
Updated the Pastable landing page today. Rewrote the hero copy to lead with the actual pain — "stop rebuilding the same nav bar in every project" — instead of describing features. Also added a quote from a developer on the waitlist. Small changes but the old copy felt too vague. We'll see if conversion improves. #buildinpublic #webdesign
Webflow's Shared Libraries are great — if all your projects live in one Workspace. But freelancers juggling client workspaces? Agencies moving components between accounts? That's still manual copy-paste.
And if you're also working in Figma? Forget about it. The cross-tool gap is still wide open.
@allinonetools Exactly — and the temptation to add features never stops. Every conversation, someone wants folder sync, team sharing, version history. But the core loop has to work perfectly first. If copy → save → paste doesn't feel instant and reliable, nothing else matters.
Updated the Pastable landing page today. Rewrote the hero copy to lead with the actual pain — "stop rebuilding the same nav bar in every project" — instead of describing features. Also added a quote from a developer on the waitlist. Small changes but the old copy felt too vague. We'll see if conversion improves.
I can spin up a full Figma design system in minutes now. But when I start my next project, I'm back to square one because nothing carries over cleanly between Figma files, let alone between Figma and Webflow.
We keep building better ways to generate design systems from scratch, but nobody's solving the boring problem: actually reusing components across projects and tools.
How do you handle this? Genuinely curious.
honestly, the weirdest part of shipping isn't the bugs—it's having something that works but watching it sit there. built pastable to solve the component reuse mess across figma/webflow/html, got early users excited, but... radio silence
what's the missing piece between "that's cool" and "i'm actually using this"?
That framing clicks — standardize upstream, move downstream. I like it.
I'm still in week 1 of real testing, so being honest about where things are. But the split feels natural: Palette Pro catches token drift before it becomes a problem, Pastable handles moving the component across tools.
Once I validate the workflow with testers, let's revisit the guide idea.
Interesting observation from digging into clipboard formats:
Everyone talks about Figma MCP as the design-to-code bridge. But MCP only gives you API access — it can't touch your clipboard.
When you copy in Figma, it's Kiwi (proprietary binary). Webflow uses XscpData. These carry the real component data and they're invisible to MCP.
The gap between "AI reads your Figma file" and "you can move components between tools" is bigger than people think.
@allinonetools This resonates. We designed Pastable around exactly that loop — copy a component, it saves to your library, paste it back when you need it. Three steps, done.
The temptation to add AI tagging, search filters, and organization features is real. But early testers just want to copy→save→paste without thinking.
Week 1 of real user testing.
First Webflow veteran is trying Pastable today — someone who's been building sites for 13 years. They want to use it on a real client project.
I spent yesterday fixing preview rendering so components actually look right in the library. Small thing, but it's the difference between "this feels broken" and "oh I can actually see what I saved."
Nervous but excited. If it works for someone at that level, we're onto something.
@chadtd1 Yeah that could work. Right now I'm keeping things simple — Pastable doesn't touch tokens at all, it moves the full component structure. So there's no real conflict to manage on my end.
A workflow guide sounds interesting. What are you thinking — like "clean your tokens with Palette Pro, then move components with Pastable"? Would help people juggling both tools.
@whykislay Thanks Kislay! Would love to be listed on buildinprocess.com. We're in early alpha — pastable.app has all the details. Happy to share anything you need for the listing!