Graphic Design File Handoff Checklist for Clients and Developers
A finished design is useful only if the next person can find the right file and use it for its intended purpose. A website developer needs assets that fit the site. A printer needs artwork prepared to its production specifications. A client may need a logo for an upcoming presentation and an editable master for a future project. Sending every file in one folder leaves those decisions to the recipient.
Set deliverables by intended use
Write down each place the design will appear before choosing formats. A logo for a website may need a scalable version, a transparent image and a version that works on a dark background. A social graphic needs the dimensions of its actual placement. A brochure sent to a printer needs an output file made to that printer’s specifications. One export rarely serves all three purposes well.
Ask the recipient what their system accepts. A developer may prefer SVG for a simple logo but request PNG for a particular interface or email template. A printer may specify a PDF preset, trim size, bleed and colour requirements. Record those answers beside the deliverable so the package reflects the receiving workflow rather than an assumed industry default.
These are starting points, not automatic export settings. Canva’s file-quality guidance distinguishes JPG and PNG uses from PDF Print and cautions that a high-quality export cannot repair a poor source image. Inspect the actual output at the size in which it will be used.
Package the outputs people are meant to use
Put approved exports in a clearly named Final folder. Separate web assets from print artwork if the job has both. Within the web folder, group files by placement or asset family, such as Logo and Campaign_Banners. Include only the variants with a purpose. A folder full of near-identical experiments makes it harder to select the approved version.
Use file names that answer three questions without opening the file: what is it, which use is it for and which version is current? For example, Northstar_Logo_DarkBackground_v03.svg and Northstar_Brochure_Print_v03.pdf identify different deliverables. Keep the same version number across related exports made from one approved revision. If the artwork changes, increase the version number and replace the delivery note. Avoid names such as final-new-2 or a date alone; neither explains which file supersedes which.
Decide whether editable source belongs in the handoff
An exported logo or PDF is not necessarily a working master. Adobe’s Illustrator file guidance explains that exported, non-native formats may not retain all the data needed when reopened for editing. If future editing is part of the agreed deliverable, identify the native file and the application required to open it. Do not describe a flattened image as an editable source file.
Make the source-file decision explicit before assembling the package: included, not included or to be agreed. If included, supply the agreed working file separately from finished exports and state what parts the recipient may need to license or replace. A source file can contain linked photographs, placed illustrations, fonts or other dependencies that are not carried with a simple export. Check the file from the delivery folder, not only from the designer’s original workstation.
For an InDesign job, Adobe’s packaging instructions describe collecting the working document, linked graphics and a report after checking for missing links or fonts. The packaging options can also include a print PDF. That can be useful when a printer or collaborator needs the working document, but the package still needs a human check: confirm the links resolve, the PDF is the approved output and every included asset may be shared.
Treat font files as a separate permission decision
Listing the typefaces used in a project is different from sending the font files. Adobe Fonts’ licensing guidance says many font licences do not permit passing font files to a third party without appropriate rights, and that terms vary by licence. Check the licence for each font before including it. If sharing is not permitted, name the typeface in the usage sheet and tell the recipient that they need their own valid access to edit the work.
A PDF can preserve the appearance of type for viewing or printing without handing over installable font files, subject to the applicable embedding terms. It does not give the recipient the right or the practical means to create new designs with that font. Record the choice plainly: font files supplied under confirmed terms, recipient obtains its own licence or finished PDF only. Apply the same deliberate check to stock images and other licensed material included with editable source.
Give the client a short usage sheet
A plain-language note can prevent more mistakes than another export. Keep it in the package as Read-Me.txt or an equally easy-to-open document. State which folder contains the approved files, what each variant is for and which file a printer or developer should use. Explain colour variants in ordinary terms: “Use the white logo on dark backgrounds” is clearer than a filename alone.
Include the approved colour values and typeface names if they are part of the delivered identity. Note any limits that affect use, such as a logo version that becomes illegible when made small or an image licensed only for specified contexts. If the design has a transparent background, say so. If a print file must be sent unchanged to the named printer specification, say that too. Keep the note specific to the files delivered; a generic brand guide should not force someone to search for the one instruction they need.
Verify delivery from the recipient’s side
Before sending, open the package as though it came from someone else. Extract it to a new location if it is compressed. Open a sample of every format, inspect every intended page or artboard and compare the visible content with the approved version. Check that filenames in the usage sheet match the files present. For a source-file handoff, open the copied working file and check for missing links or font warnings.
Then ask the recipient to confirm two things: they can access and open the files, and they can identify which version is approved for their task. A developer should be able to point to the intended web logo and its variations. A printer should be able to identify the production PDF and the specification it was made for. If their software rejects a format or a dependency is missing, correct the package and issue a newly identified version. A successful upload or download alone does not establish that the files are usable.
Final-delivery worksheet: digital track
Use these checks for web, email, presentation and social assets. Fill in the actual placement and recipient rather than treating the list as proof that every platform accepts the same file.
- Destination: Record each website component, channel or document that will use the asset, plus the person receiving it.
- Formats and sizes: Confirm accepted formats, required dimensions and any transparent or dark-background variants. Check exports at their displayed sizes.
- Content: Verify that the exported files show the approved wording, crop, logo version and colour treatment.
- Editable source: Mark “included”, “not included” or “to be agreed”. If included, name the application and check linked assets.
- Fonts and image rights: Record whether files can be shared, whether the recipient needs its own licence and whether any supplied image has a use restriction.
- Delivery test: Have the recipient open a representative file and identify the approved package version.
Final-delivery worksheet: print track
Use a separate record for each printed item or variation. The printer’s supplied requirements govern the output; do not substitute a setting copied from another job.
- Production specification: Record the printer, finished size, page or panel count, bleed and other requested PDF settings.
- Delivered output: Name the exact production PDF and its version. Open that PDF and inspect every page, including fronts, backs and small text.
- Working package: If the printer needs editable artwork, state that the source is included and confirm linked graphics open from the delivered folder. Otherwise, state that the PDF is the deliverable.
- Font decision: Record whether the printer relies on the PDF, has its own licensed font access or may receive font files under confirmed licence terms.
- Recipient check: Ask the printer to confirm that it can open the supplied file and has identified the intended production version.