Brand Assets Library: Logos, Colors, Fonts, and Videos

A brand assets library is a maintained place where people can find approved brand files and the instructions for using them. A useful library usually brings together logo variants, color values, typography guidance, imagery, templates, videos, and a brand book. The exact contents and permissions are controlled by each brand owner, so never assume that one company’s rules apply to another.

What belongs in a brand assets library?

Official examples show a recurring set of materials, although no universal checklist exists.

Asset or guidance	What to store	Questions to answer
Primary logo	Master vector and approved raster exports	Which backgrounds, sizes, and contexts are allowed?
Alternate marks	Horizontal, stacked, symbol-only, inverted, and monochrome versions	When should each variant be used?
Colors	Named tokens and values such as HEX, RGB, CMYK, or Pantone where supplied by the owner	Which values are for screen, print, accessibility, or specialty production?
Typography	Typeface names, weights, styles, web files, and licensing source	Can this team legally use the font, and where is the license?
Icons and illustrations	Approved icon sets, line weights, and illustration files	Can files be edited or recolored?
Photography and imagery	Originals, crops, usage notes, credits, and expiration dates	Where may each image appear?
Templates	Presentation, social, document, email, and campaign templates	Which fields may contributors change?
Video and audio	Master files, compressed versions, captions, transcripts, and music licenses	Are there press, partner, regional, or date restrictions?
Brand book	Rules, examples, accessibility guidance, and approval contacts	What is required, recommended, or prohibited?

Ankr’s official asset page groups logos, fonts, brand colors, partnership templates, and videos; Scaleflex shows a portal model with a complete kit and individual downloads; Western Digital separates approved corporate logos from press B-roll; and Brave publishes logos, colors, and typography guidance together. These examples demonstrate common patterns, not a standard every organization must follow.

How to organize the library

1. Separate masters from exports

Keep editable master files in a controlled area and provide ready-to-use exports beside them. For each file, record the variant, color treatment, intended background, format, dimensions, owner, and last approval date. A filename such as brand-symbol-white-dark-bg.svg is more useful than final-logo-2.svg.

2. Make variants obvious

Use folders or metadata for full-color, inverted, monochrome, symbol-only, horizontal, and stacked marks. Shopify’s examples distinguish full-color, inverted, and monotone marks and show incorrect uses such as stretching, rotating, recoloring with gradients, or placing a logo on a low-contrast or busy background.

3. Store reusable color values

Publish values in a copyable format and explain where each value applies. A design token file can sit next to the human-readable guide:

:root {
  --brand-primary: #123456;
  --brand-secondary: #789abc;
}

Use only values supplied or approved by the brand owner. Do not derive “close enough” values from a screenshot.

4. Identify fonts and licensing sources

List the exact family, weights, styles, and where each person can obtain it legally. Ankr identifies Inter as its body font under the Open Font License and separately describes TT Firs Neue Demibold as a premium typeface whose license must be obtained from the type foundry. Treat those as examples; verify the terms for the particular font your brand uses.

5. Put rights beside the file

Do not hide permissions in a separate policy page. Add a short rights field, credit requirement, territory, audience, expiration date, and approval contact to every photo, video, audio track, and partner asset. Automattic distinguishes materials for the company and licensed partners from editorial use of images, audio, and video. Western Digital describes its B-roll as available for press and media use. Those restrictions are owner-specific.

6. Offer both a complete kit and single-file downloads

A portal should support someone who needs the whole package and someone who needs one logo in seconds. The Scaleflex example demonstrates this two-level approach. Include previews, file sizes, formats, and a direct download action.

Permission and trademark checks

Before publishing an asset, answer these questions:

• Is the file from the brand owner’s current official location?
• Is this use authorized for your organization, campaign, territory, and audience?
• Could the placement imply sponsorship, affiliation, endorsement, or ownership?
• Are attribution, editorial, press, partner, or reseller conditions attached?
• Is the file still current, or has a newer master replaced it?
• Does the use preserve the owner’s required clear space, contrast, and minimum size?

Shopify states that “Use of our brand assets must be expressly authorized in writing.” Its Shopping Bag guidance specifies a minimum width of 80 pixels or 28 millimeters, but that measurement belongs to Shopify and must not be generalized to other marks. Always follow the current owner instructions.

Choosing a public page, portal, or private repository

Approach	Best for	Trade-offs to check
Public download page	Press, developers, and partners who need quick access	Permissions may be easy to misunderstand; stale files are visible to everyone
Access-controlled portal	Licensed partners, agencies, and regional teams	Requires account administration and a clear request path
Complete kit plus individual files	Mixed audiences with different needs	Keep both levels synchronized
Internal repository	Employees and production teams	External users need a separate approved distribution channel

Compare options by public versus restricted access, single-file versus complete-kit downloads, the depth of logo/color/font guidance, rights information for media, and whether the source is the brand owner’s current official location. Digital guideline platforms can organize colors, typography, logos, images, and other content blocks, but verify current features and pricing before selecting one.

A maintenance workflow that stays reliable

1. Assign ownership. Name the brand or legal owner and a day-to-day library maintainer.
2. Approve a canonical set. Retire duplicates and mark old files as archived rather than leaving ambiguous “final” copies.
3. Attach metadata. Record variant, format, dimensions, license, audience, territory, expiration, and approval date.
4. Publish usage examples. Show correct and incorrect logo placement, contrast, spacing, cropping, and color use.
5. Validate downloads. Open vector files, inspect fonts, check video playback, and verify that links work.
6. Review on a schedule. Recheck the live owner page before major campaigns and whenever a rebrand, legal change, or license renewal occurs.
7. Announce changes. Tell teams what changed, what was retired, and where the new canonical files live.

Creating visual references for a library

A screenshot of an approved asset page can help a team document where a file came from, compare a portal over time, or include a visual reference in an internal handoff. Capture the whole page when the relationship between sections matters; capture one element when you need a single logo card or color specimen. Check the result for cookie banners, newsletter popups, chat widgets, lazy-loaded images, and permission-sensitive content before distributing it.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. Before capture it accepts consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets, with each step configurable. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and whether the shot was billed.

See the ScreenshotNeo API documentation for all options, including full-page and selector capture, device presets, dark mode, custom CSS and JavaScript, waits, headers, cookies, blocking rules, caching, signed links, async webhooks, bulk capture, and PDF output.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://screenshotneo.com \
  -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://screenshotneo.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://screenshotneo.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));

Replace the example URL with the public brand asset page you are documenting. Use a selector when only one approved file needs to be shown, a wait condition when assets load asynchronously, and a cache TTL when the page changes infrequently. For an AI-assisted workflow, the MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients.

There are 1,000 free screenshots each month with no card. Paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.

Troubleshooting

Problem	Likely cause	Fix
A logo looks blurry	A raster export was enlarged	Use the approved vector or a raster file at the required output size.
The mark looks wrong on a dark background	Wrong color treatment	Choose the approved inverted or light variant.
A downloaded font cannot be used commercially	License scope was not checked	Read the typeface license and obtain it from the named source.
A partner cannot open a file	Access control or expired permission	Confirm the audience restriction and provide the current approved channel.
A screenshot contains a popup	Consent, newsletter, or chat UI loaded before capture	Use a consent-aware capture flow, hide selectors, or configure the relevant cleanup step.
A capture is blank or times out	The page failed to load, requires a wait, or triggered a bot check	Inspect the page manually, add a selector or delay wait, and check the response verdict headers.
The library has conflicting “final” files	No canonical owner or archive process	Choose one approved master, archive older versions, and add dates and metadata.

Performance, reliability, and cost considerations

• Performance: Prefer a specific element capture when a full page is unnecessary. Use caching for stable pages and a chosen wait condition instead of an excessive fixed delay.
• Reliability: Keep source URLs and approval metadata with every screenshot. Re-capture after a rebrand or portal change. For recurring jobs, use async jobs and signed webhooks.
• Cost: ScreenshotNeo bills only clean shots; bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. Bulk capture supports up to 100 URLs per call. The usage API helps reconcile consumption.
• Output: Select WebP or JPEG for compact previews, PNG for lossless graphics, and PDF when a complete reference document is required.

FAQ

Is there a universal list of files every brand library must contain?

No. Logos, colors, fonts, imagery, templates, videos, and rules recur across official examples, but each owner decides what to publish.

Can I reuse a logo found in a search result?

Use the current official owner page and verify authorization, audience, placement, and trademark restrictions first.

Should every font in the brand guide be free?

No. A guide should identify the licensing source and permitted use. Premium typefaces may require a separate license.

When should I use a complete brand kit?

Use it for onboarding or agency handoffs. Use an individual download when you need one approved file quickly.

Is a screenshot a substitute for the original asset?

No. A screenshot documents appearance or provenance; production work should use the approved downloadable master file.