How to use
01
Detect the assets
Paste the site URL and click Detect assets. The tool reads the page's public metadata and reports the hostname along with the logo, favicon, and OG image it located.
02
Choose what goes in the pack
Tick or untick the checkboxes: Logo (from og:image), Favicon, OG image, colors.json, and fonts.txt. Anything unticked stays out of the ZIP, so you only ship what the project needs.
03
Download brand pack ZIP
Press the button and the tool fetches each selected file, adds a README with the extraction date, and saves everything as hostname-brand-pack.zip ready to drop into your project folder.
Why Brand Asset Pack
- One-click ZIP with a site's logo, favicon, OG image, colors.json, fonts.txt.
- Great for competitive research, design briefs, and brand audits.
- All sourced from publicly-visible metadata, no scraping or auth.
Common questions
What files end up in the brand asset pack ZIP?
Up to five items depending on your checkboxes: the logo pulled from og:image, the favicon, the OG image itself, a fonts.txt listing detected Google Fonts, and a colors.json file. A README.txt with the source host and extraction date is always included, and the archive is named after the site's hostname.
Where does the asset pack's logo actually come from?
From the site's og:image meta tag, which is the most consistently published brand image on the web. It's sometimes a social card rather than the clean mark, so if you need more candidates, run the Logo Extractor, which also checks schema.org markup, the favicon, and img tags.
Does the asset pack contain the site's full color palette?
Not yet. The colors.json file is a metadata placeholder that points you to the Brand Color Extractor, which does the deep CSS scan and returns ranked hex values. Run that tool separately and drop its output into the same folder to complete the kit.
How does the asset pack detect the fonts?
It scans the raw HTML for fonts.googleapis.com links and parses the family names out of them into fonts.txt. That means self-hosted @font-face families and Adobe Fonts won't appear; the Brand Font Detector covers those cases with a full stylesheet scan.
Can I download brand assets from a competitor into an asset pack?
Yes, everything comes from publicly visible metadata, the same data any browser receives, so building a research pack is fine. Usage rights are separate: a competitor's logo and imagery remain their property, so keep extracted packs internal to research and pitch work.
Why is the favicon missing from my asset pack?
Either the site never declares a favicon link in its HTML or the file's host refused the fetch. Try requesting /favicon.ico on the domain directly, and if you're rebuilding the client's icons anyway, the Favicon Generator produces a complete replacement set from one image.
Is the asset pack assembled on a server or in my browser?
The individual files are fetched through a small proxy endpoint, but the ZIP itself is assembled in your browser with JSZip and saved straight to disk. Nothing is stored anywhere, so each pack exists only in your download folder.