Back
Team AssetSnip

How to Extract Colors, Fonts, and Assets from Any Website (with AssetSnip)

A step-by-step guide to extracting color palettes, font stacks, SVGs, gradients, Lottie animations, and export-ready code from any live website using the AssetSnip Chrome extension.

How to Extract Colors, Fonts, and Assets from Any Website (with AssetSnip)

Why screenshots are not enough

Design research usually starts on a live website. You see a color palette that works, a type hierarchy that reads well, or a hero animation that feels polished. A screenshot captures the look, but not the values behind it. You still need the hex codes, the font-family declarations, the gradient stops, and sometimes the actual SVG or Lottie file.

AssetSnip is a Chrome extension built for exactly that workflow. It reads the live page, surfaces the design values and media assets by type, and lets you save everything to an organized library. This guide walks through the full extraction process step by step.

Prerequisites

  • Google Chrome (latest stable version) with the AssetSnip extension installed
  • An AssetSnip account. Sign in on the web app so captures sync between the extension and your library.
  • A target page you are allowed to analyze. Always respect copyright, robots directives, and the site's terms of use when saving or republishing assets.

Step 1: Open the target page and launch the side panel

Navigate to the page you want to extract from. Let the page load fully so that images, web fonts, CSS, and animation bundles resolve completely. Lazy-loaded content may require scrolling down first.

Click the AssetSnip icon in the Chrome toolbar to open the side panel. The extension scans the current document and populates tabs for each asset type.

If the panel appears empty, click Rescan. This re-runs the content script on the current document, which helps after single-page app navigations or late-loading content.

Step 2: Extract the color palette

Open the Colors tab. AssetSnip reads computed styles across the page and presents a ranked list of color values, organized by frequency. You will typically see:

  • Primary and accent colors used on headings, buttons, and links
  • Background and surface colors
  • Text colors in different weights

Each color shows its HEX value by default. Click to copy it, or save it to your library for later reference. This is faster and more accurate than eyedropping a screenshot, because you get the exact value the browser renders, including any alpha or dark-mode overrides.

Step 3: Capture CSS gradients

Switch to the Gradients tab. AssetSnip extracts the actual CSS gradient strings from the page, including linear-gradient, radial-gradient, and conic-gradient definitions.

This is especially useful for hero backgrounds and decorative elements where the gradient has multiple stops. Instead of trying to recreate it from a bitmap, you get the exact CSS you can paste into your stylesheet or theme file.

Step 4: Identify fonts and type styles

Open the Fonts tab. AssetSnip surfaces every font-family the page uses, along with the sizes and weights where each face appears. This gives you a practical reference for:

  • Which typefaces to license or load from Google Fonts
  • The type scale (size and weight combinations) the page uses
  • Whether the page relies on system fonts, variable fonts, or multiple families

If you only need font data for a specific section rather than the whole page, skip ahead to Inspect mode for scoped results.

Step 5: Collect images, SVGs, and media

The Media tab lists raster images (PNG, JPG, WebP, AVIF), inline SVGs, and favicons found on the page. Each item has a preview thumbnail and quick actions to copy, download, or save to your library.

SVGs that are inlined in the HTML appear as clean, copy-ready vector markup. This is typically how icon systems and logo assets are served on modern sites.

For pages that use animation, the Lottie tab shows any Lottie JSON files the page loads. You can preview the animation, download the JSON, or save it directly. The Videos tab captures MP4, WebM, and GIF references with the same save-or-download options.

Media, Lottie, and video downloads count against your plan's monthly limits. Check the pricing section for the numbers on each tier.

Step 6: Use Inspect mode for a specific component

Sometimes you do not need the entire page. You need the exact styles and markup for a single card, hero block, or navigation bar. That is what Inspect mode is for.

  1. Toggle Inspect mode on in the side panel.
  2. Hover over the live page. You will see a highlight outline tracking the element under your cursor.
  3. Click the element you want. AssetSnip captures the selected DOM subtree.

The panel then shows multiple output tabs:

  • HTML: the raw markup of the selected region
  • CSS: computed style declarations for the elements
  • Tailwind HTML: class-based markup using Tailwind-style utility classes
  • Tailwind Config: a theme snippet you can adapt for your tailwind.config file
  • React: a component-style string for quick prototyping

You can also download standalone HTML for the region, or open it in CodePen to test the component in isolation.

Not every tab will be fully populated for every selection. Output quality depends on the page structure, and shadow DOM or heavily dynamic rendering may produce lighter results. On typical marketing pages, landing pages, and component showcases, you will get substantial output.

Step 7: Save to your library and organize

Every item you save from the extension lands in your web app library with the source URL recorded. From the library you can:

  • Filter by type: images, SVGs, colors, fonts, gradients, videos, Lottie, captures, AI icons
  • Tag items with keywords like "fintech reference," "hero patterns," or "Q3 audit"
  • Create folders to group captures by project, client, or research theme
  • Bulk export selected items as a ZIP archive (paid plans)
  • Copy values or download files individually at any time

The library is persistent and searchable. Instead of a pile of bookmarks or a folder of screenshots, you have a structured collection with the actual values and files attached.

Bonus: Generate SVG icons with AI

The web app dashboard includes an AI SVG generation tool, separate from the extension's extraction workflow. You can:

  • Type a text prompt (like "minimalist shopping cart icon") to generate a new SVG
  • Upload a raster image to vectorize it into clean SVG format

Generated icons save to the same library as your captured assets. AI usage is metered per plan, with credits resetting each billing cycle. This is useful when you need a quick custom icon without switching to a dedicated vector editor.

Tips for better results

  • Let the page finish loading before opening the panel. Lazy images and deferred fonts need time to resolve.
  • Scroll through the page first to trigger lazy-loaded sections, especially on infinite-scroll layouts.
  • Use Rescan after single-page app navigations. The extension does not automatically re-scan when the URL changes via client-side routing.
  • Combine Colors and Inspect results to build a theme file. The Colors tab gives you the global palette; Inspect gives you the Tailwind config snippet for a specific component.
  • Respect copyright. AssetSnip makes it easy to capture assets, but that does not grant you the right to republish copyrighted images, icons, or animations without permission.

Free plan vs paid plans

The free plan includes 20 downloads per month, 15 saved items, 5 Lottie exports, 5 gradient exports, and limited Inspect captures. It is enough to try the workflow on a few pages and see if AssetSnip fits your process.

Paid plans (starting at $7/month) unlock higher limits on every dimension: more downloads, more saves, more Inspect and Lottie exports, AI icon credits, folder organization, and bulk ZIP exports. The yearly plan at $49/year offers the best value for consistent use. See the full comparison on the pricing page.

Next steps

You now have a repeatable path from "I like this site" to "I have the exact values, files, and markup I need," without rebuilding the same manual DevTools session every time.