OWNER GUIDE · REVIEWED 9 SEPTEMBER 2026
What logo files should you receive from a designer?
Start with where logo must work, then check files, variants and references against those uses. Format names alone do not prove quality, rights or originality.
Turn uses into a cardStart with intended uses, not file extensions
Write down where logo must appear during next year: website header, social avatar, email signature, printed menu, shop sign, workwear, packaging or another real placement. Each context creates different shape, size, background and production constraints.
Wide website navigation may need horizontal lockup. Square avatar may need icon-only mark. Dark photography may need reverse version. Stamp or embroidery may need one-colour artwork. Professional print may need vector data and printer-specific colour setup.
Do not ask for every possible export by default. Ask whether delivered package covers uses agreed with designer. Card turns selected contexts into file questions without uploading artwork.
Identify editable master
Ask which file controls future changes and which application opens it. Native source might be an Illustrator, Affinity Designer or another project file; SVG, EPS or PDF may also carry vector artwork. Extension alone does not show whether text, layers, linked assets or effects remain editable.
Keep exported copies separate from master. Record filename or folder location privately in your own storage, not in Logo Handoff Card. If designer promises source later, mark it promised rather than received until file arrives and opens.
- One named master or source of truth
- Opening software and version understood
- Linked fonts or assets identified where relevant
Check digital exports in real placements
Transparent PNG works in many everyday tools. SVG can stay sharp at different browser sizes. Neither guarantees correct proportions, spacing or legibility. Open delivered files and place copies into actual header, profile image or document template before closing project.
Check whether background is genuinely transparent, whether small text survives target size and whether excess empty space makes mark appear tiny. A large full logo may still fail as favicon or social avatar; request icon-only variant when needed.
Separate layout, background and colour variants
Logo package often needs more than one arrangement. Primary lockup may combine symbol and name. Secondary lockup may stack them. Icon-only mark serves small or square uses. These are separate design decisions, not resized copies.
Full-colour artwork may disappear against dark image or fail when production method permits one ink. Reverse version is prepared for dark background. One-colour version removes reliance on gradients and multiple colours. Record each required variant against context that needs it.
Ask printer before calling files print-ready
Professional printers, sign makers and garment suppliers may ask for different vector formats, colour modes, spot colours, bleed or cut paths. Logo handoff cannot predict every supplier. Send specification to designer before final export where possible.
Do not treat filename containing ‘print’ or ‘CMYK’ as proof. Ask supplier to confirm file opens and meets job. If supplier is not chosen yet, keep print requirement visible as unresolved rather than accepting unsupported assumption.
Keep colour and type references usable
Record agreed colour values for tools people will use: HEX or RGB for screens, plus CMYK or spot-colour references where print agreement requires them. Conversion between systems can change appearance, so references should say which value controls which use.
Ask for typeface names and styles used in logo or supporting lockup. A font name does not grant licence or provide font file. Record where licence came from and who needs future access. If lettering was converted to outlines, keep original type reference for future consistency.
Keep source declarations separate from rights conclusions
Ask designer to identify stock artwork, icons, typefaces or other declared third-party material. Keep contract, invoice, licence records and approval messages with project. Logo Handoff Card records whether source note arrived; it does not determine copyright ownership, licence scope, originality or trademark availability.
Where contract or rights are unclear, pause acceptance question and obtain qualified legal advice. A complete technical file set and clear legal position are different facts.
Run final logo handoff check
Open each important file, compare it with approved direction and test highest-risk contexts. Mark received only when item exists. Keep promised items open. Mark not applicable only when context truly does not need item, not because file is missing.
- Intended uses named and mapped to required variants
- Editable master and opening application identified
- Transparent, small, dark and one-colour needs checked
- Printer requirements confirmed where print is imminent
- Colour, type and declared source notes retained
- Every promise either received or left visibly unresolved
Use worked café example to see difference between received, promised and unresolved items. Then build browser-local card for your commission; no logo artwork or filename leaves device.