Every designer and developer has a version of the same problem: a folder called inspiration/, a Notes app full of pasted hex codes, a Downloads folder with half-remembered screenshots, and 40 open browser tabs they're afraid to close because they might need them later.
The AssetSnip library is the answer to all of that.
What the library is
Every asset you save — a color palette, a font, an image, an SVG icon, a video clip — lands in your AssetSnip library, permanently linked to the source URL.
The library lives in your dashboard at /dashboard/library and is organized by asset type:
| Tab | What's in it | |---|---| | Colors | Palettes and individual swatches with their hex, HSL, and WCAG contrast values | | Fonts | Font families, detected weights, size scales | | Images | PNGs, JPGs, favicons — downloadable, with the source URL | | Icons | SVGs, including AI-generated icons from the AI tab | | Videos | Embedded video and animation references |
Saving from the extension
From the AssetSnip side panel, every captured asset has a Save button. Tap it and the asset goes to your library immediately. You can save:
- An individual color swatch
- A full palette from a page or section
- A specific image
- The entire font system of a site
- Individual SVG icons
You're in control of what goes in. There's no automatic hoarding — only what you deliberately save.
Searching and revisiting
The library is searchable by name, tag, and source domain. If you saved a palette from linear.app three weeks ago, searching "linear" brings it up instantly — no scrolling, no trying to remember which folder you put it in.
Each saved item shows:
- A visual preview
- The source URL with a link back to the original site
- The date it was saved
- Available actions (copy, download, export)
The AI icons tab
If you've used the built-in AI icon generator, your generated icons appear in the library too — in the AI tab. They're stored as SVGs with your original prompt as the description, so you can find them by searching for what you asked for.
Why this beats a screenshot folder
The problem with screenshots is that they're static, untagged, and unsearchable. A library of captured assets is searchable, actionable (you can copy a hex code without re-opening DevTools), and always current since it links back to the live source.
When your project needs a reference six weeks after you did the initial research, the library is still there, organized exactly how you left it.
The library doesn't require any extra work to maintain. Save as you go while browsing, and the organization happens automatically. That's the whole point — less overhead, more building.