GitBrand
  1. Home
  2. Guides
  3. Logo package for clients

Guide 06 · Handoff

How to package logo files for a client.

A good logo package lets the client use the identity for years without asking you. That means the right formats, the right color versions, names that explain themselves, a note on fonts and licensing, and a delivery method that stays current.

By the GitBrand teamUpdated September 23, 20267 min read

  • Deliver vector (SVG, plus AI or EPS if agreed) and transparent PNG
  • Include full-color, one-color, black and white versions
  • Name every file by variant and background
  • State the font licensing situation in writing
  • Deliver as a live link so the package stays current
north-logo-package/
├── README.txt
├── primary/
│   ├── north-primary-fullcolor-on-light.svg
│   ├── north-primary-fullcolor-on-dark.svg
│   ├── north-primary-onecolor-forest.svg
│   ├── north-primary-black.svg
│   ├── north-primary-white.svg
│   └── png/
│       ├── north-primary-fullcolor-on-light@1x.png
│       └── north-primary-fullcolor-on-light@2x.png
├── symbol/
│   ├── north-symbol-fullcolor.svg
│   ├── north-symbol-black.svg
│   └── north-symbol-white.svg
├── wordmark/
│   ├── north-wordmark-ink.svg
│   └── north-wordmark-paper.svg
├── print/
│   └── north-primary-cmyk.pdf
└── social/
    ├── north-avatar-512.png
    └── north-favicon-32.png
An ideal package for the North mock brand. Every file name says brand, variant, color version and background.
1 / 5

The formats to include

Vector is the master. Provide SVG for web and modern tools, and AI, EPS or PDF if the client's printers or agencies need them. Then provide transparent PNGs at a few useful sizes for the people who will never open a design tool. Skip JPG unless requested; it has no transparency and adds confusion.

FormatIncludeScalesTransparentNote
SVGPrimary, symbol, wordmarkThe master. Every other file can be exported from it.
PNGTransparent, at 1x and 2x for common usesFor people who will never open a design tool.
PDF or EPSFor print, if in scopeWhat print suppliers and older agencies ask for.
JPGOnly if requestedNo transparency; adds confusion. GitBrand exports it on demand when needed.
Favicon and avatarSquare crops, if in scopeSaves the client from cropping the symbol badly.
2 / 5

The color versions to include

Full color on light, full color on dark, single color, black and white. Not every brand needs every version, but a client who only has full-color-on-light will improvise the rest, badly. Deliver the versions you would want them to use and label the background each belongs on.

North
Full colorDefault on light backgrounds
North
One colorSingle ink, embroidery, stamps
North
BlackFax, forms, documents
North
WhiteDark backgrounds and photography
3 / 5

Names and structure

Structure the package by variant, then color version, then format, or flatten it entirely with descriptive names. Either way, a filename should say brand, variant, color version and background. A one-page readme explaining the structure saves you a call.

{brand}-{variant}-{color}-{background}.svg → north-symbol-white-on-dark.svg

brand
north
Files travel; the name tells whose logo it is.
variant
primary · symbol · wordmark
Which lockup this is.
color version
fullcolor · onecolor · black · white
What ink or pixels it uses.
background
on-light · on-dark
Where it belongs, so nobody guesses.
format
.svg · .png · .pdf
Left to the extension; never in the name.
4 / 5

Fonts and licensing

Say which typefaces the identity uses and where the client licenses them. Do not redistribute font files unless the license allows it. If a font is open source, link to it. If it is commercial, tell the client they need their own license and what it is for. This protects both of you.

Write these three lines into the readme

  • Which typefaces and weights the identity uses, for headings and body
  • Where each is licensed, with a link, and whether files are included
  • A fallback the client may use when the brand font is unavailable in a tool

In a GitBrand repository, fonts have a live preview where the client types their own text and adjusts the size, and downloads are offered only where you have chosen to include the files.

5 / 5

Deliver a link, not a zip

A zip is complete on the day you send it and stale a month later. A GitBrand repository holds the same package with previews, on-demand PNG and JPG exports, named colors, font previews and your usage notes beside each asset. Password-protect it during the project and open it at launch. When something changes, update the repository and the client's link keeps working.

The zip

  • Correct on the day it is sent
  • Forwarded, renamed and split across inboxes
  • No previews; people open files to see what they are
  • A change means a new zip and a new email

The link

  • gitbrand.com/north, one address that stays current
  • Public, password-protected or member-only, same link
  • SVG in, SVG / PNG / JPG out, at the size they need
  • Colors, fonts, resources and FAQ beside the logos
FAQ

Client package questions

Should I include the source files?

That depends on your contract. Many designers deliver editable source files as a separate, explicitly scoped item. The logo package is the usable output, not the working file.

What sizes should the PNGs be?

Enough to cover common uses without guessing: for example 500 px, 1000 px and 2000 px wide. Since GitBrand exports from the SVG on demand, the client can also export the exact size they need.

How do I deliver a package for a brand with sub-brands?

Use one repository per sub-brand and clone the primary repository as a starting point. Shared elements stay consistent and each brand has its own link.

Should the package include a readme?

Yes, one page: what each folder holds, which version goes on which background, and where fonts are licensed. In a GitBrand repository the same notes sit beside each asset and in the FAQ section, so the readme is the interface.

Related

  1. For agenciesOne repository per client, password-protected until launch.
  2. Logo file formatsSVG, PNG or JPG, and when each is right.
  3. For designersHand off the identity without the follow-up emails.
  4. All guidesSix short guides on building and sharing a brand kit.

Hand over a link that stays current

Build the package as a free GitBrand repository, keep it password-protected during the project and open it at launch. Up to five repositories on the free plan.