A logo package people can use without calling the designer
Choose logo variants for backgrounds, formats for tools and a handover teams and partners can use without guessing.
Article language: English

In this article
A white logo on a transparent background opened in a light preview looks like a bold artistic decision: there is nothing there. The person preparing a presentation asks for a “normal file”. They receive the same mark on a black rectangle and paste it onto a navy slide. A neat black island remains around the logo. Everything followed the supplied files, yet nobody is happy.
This is a hypothetical situation where the mark need not be redesigned. Its handover needs design. A logo package should help someone choose the right version for the background, placement and tool. Exporting ten file extensions alone will not do that. The recipient needs to recognise which file to open and what they may change under the agreed brand rules.
Start with the package's future users. One person will put the mark on a website, another will prepare a proposal and another will send it to a sign maker. These are different situations. The set should combine an easy everyday choice with clearly described material for production specialists. Do not make everyone learn graphics software merely to sign a company document.
Open the package as someone who did not make it
The first screen after unpacking should indicate where to start. It might be a short guide with thumbnails of variants, background examples and links to the right folders. It need not pretend to be a massive identity manual. It should answer: “I have a white proposal page and a space a few centimetres wide. What should I use?”
Organise the set by the recipient's decision, not export order. In the everyday folder show the primary variant for a light background and its counterpart for a dark one. If the brand has an approved vertical layout or symbol alone, explain their use. Do not include a historic experiment merely because it still sits beside an approved file.
Names may contain abbreviations if their meaning is available without guessing. Mozilla's Protocol Assets repository explains variant labels, including vertical, horizontal and “white” for a dark background. This is an example of a vocabulary supplied with assets, not a universal convention for every brand.
For your own team you might use names such as “horizontal-mark-light-background” and “horizontal-mark-dark-background”. If suppliers work in several languages, agree on a shared convention and explain it briefly. “Positive” or “negative” alone can be too cryptic for someone choosing a file once a quarter. They should be able to choose without knowing the designer's terminology.
A thumbnail should show the variant in its conditions of use. Display a white mark on a dark field and state alongside it that the file itself has a transparent background, if it really does. This prevents an empty preview being mistaken for damage. At the same time distinguish a demonstration board from an asset to insert. An image labelled “this is how the logo looks on navy” should not enter the production folder as an alternative mark.
Match the number of variants to actual needs. If a company uses one layout on its website and in documents, five almost identical compositions will not make work easier. If it has a separate small symbol for narrow spaces, explain when that choice applies. The mark's design and a test in the material determine the boundary, not a general rule that “a phone always needs the symbol alone”.
Treat a single-colour version separately. It may be needed where a full palette or tonal transitions cannot be reproduced. Do not tell an employee to remove colours from the primary variant themselves. Check the approved file to see which elements remain distinct and which merge into one shape. Include a small-size sample and say which technique or situation the version was made for. If that use was not envisaged, record a question for agreement instead of hiding a random black-and-white copy among finished variants.
The source folder may retain material a designer needs for further work. Separate it from everyday exports and label its role. The team should not edit a working file believing it is updating the company master. A supplier developing the identity, meanwhile, needs to know which material is the source and which is merely an export.
Also establish whether a branch name is part of the mark or text placed beside it. Test the layout using the fictional long name “Riverside Studio - Centre for Preparing Exhibitions and Displays”. If the team will add units, it needs typesetting rules and an approved example. If these are fixed compositions, provide finished variants. Do not leave a blank labelled “name here” when each department may interpret its width differently. For several marks on one board, also show the agreed arrangement rather than asking people to align random files by hand.
Choose a format for its destination
The same file can behave differently on a website, in a slide editor and at a sign maker. Ask about target tools and uses before deciding the set. The extension is part of the answer, not a guarantee. A PDF can contain a small image, and a file named “vector” still needs its contents checked.
For a raster version, stored as a grid of pixels, give dimensions and intended use. A mark 900 pixels wide and one 300 pixels wide are different assets even if a preview fits both to the same window. Do not ask a recipient to enlarge the smaller copy when you supply the right file. Conversely, a huge image need not be recommended for every small footer.

Test in the recipient's named programs: insert the file, resize it while preserving proportions, save the material and open it again. Assess background, edges and completeness of the mark in the exported result too. If a tool cannot accept one format, supply an agreed alternative and identify it in the guide. The recipient should not have to find a random converter for a task anticipated in the order. This does not require assessing every application on the market; it concerns the specific files and team's tools.
For the vector version, check the area around the mark. MDN describes viewBox as the position and dimensions of an SVG area in its own coordinate system, mapped to the display area. It describes the file's area, not simply the width of visible letters.
The practical effect is simple: two images inserted at the same width can display the mark at different sizes if their surrounding margins differ. Do not make an employee trim margins by trial and error. Establish whether the file contains the intended clear space around the mark or whether it must be supplied in the layout. Show the choice in an example and apply it consistently.
Do not equate clear space with accidental empty space after export. The first is an identity rule; the second may be a preparation error. If the mark must occupy a defined position in a website header, accept both its actual size and spacing from neighbours. The person inserting a file should not have to decide which margin the designer intended.
Assess colour against the intended background and in the final material. A variant for a dark background does not automatically work on every photograph. A bright part of an image can merge with part of the mark. An approved placement method, such as a separate field, is then needed rather than an improvised outline added in an editor. The choice and crop of these images also matter when placing the mark. The article on brand photography (in Polish) discusses their role on a website.
For print, agree requirements with the supplier of the particular item. Mark which files were prepared for that use and what must be confirmed before production. Do not present one setting as a guarantee of a correct print on every surface. A mark on paper, fabric and a sign can need separate preparation and sample acceptance.
The lettering in a mark and the font used to write company presentations also have different roles. A logo recipient should not recreate the lettering with arbitrarily similar characters. Show the finished mark in the package rules and describe communication fonts separately. If the issue is readability and hierarchy of text, examine the website typography rather than adding another logo variant. The guide to premium website typography (in Polish) discusses those choices.
Files need not multiply for every small difference. If a mark's contents are identical and two folders serve different departments, consider one designated asset instead of independent copies. If contents actually differ, the name and description should reveal it. A recipient cannot reconstruct the author's intention from a modification date.
Accept the use before accepting the archive
Test the handover with a few short tasks. A team member prepares a proposal title page on white, then inserts the mark on a dark slide and sends suitable material to a sign maker. Do not point out folder names. See whether the instructions and files suffice, and record what information was missing when they ask.
Also assess everyday editing in presentations. Can someone accidentally stretch the logo in one direction after pasting it? Does the slide master provide space without covering content? These decisions are developed in the article on a brand presentation template for a team (in Polish). The package supplies the right asset; the template helps use it without setting up everything from scratch.
The test should also include an external person if partners really receive these assets. Rather than sending the designer's entire workshop, share the approved set with its intended use described. The brand owner determines sharing rules and permitted use; the graphic guide shows how to execute that use correctly. It does not replace separate agreements with a partner.
After a mark changes, designate one place to download the current package. Your materials centre can state the set's identifier, scope and the release it replaces. The guide to a materials download centre (in Polish) discusses how to present versions. Someone returning to an old link should recognise the change. Calling the new file “final” alone will not withdraw copies sent earlier by email.
Also record which materials need checking after an update: website header, proposal, presentation template, footer and partner assets. If the palette or spacing changes too, some rules may enter your brand design tokens, named values used to implement an interface. The article on brand design tokens (in Polish) explains how to carry such rules into code. They do not replace mark files or instructions for choosing them.
Include this handover in agreements on Aeneia Design identity and brand materials: who uses the set, in which tools and with which acceptance examples. A good package does not end when every file opens. It ends when someone can choose a white mark for a dark slide without calling the designer or surrounding it with a black island.










