Brand Banner Design and Export for a Clear Agency Handoff

Use the banner maker to prepare clean images and an editable project from your own assets. This guide follows an illustrative agency assignment for Northway Learning, a training provider refreshing its social headers. The work starts with approved language and brand materials, then moves through review, export, and revision. The client uploads the finished artwork through each destination’s own controls; the maker is not an account editor or publisher.

Define the deliverable before designing the banner

Northway Learning asks its agency for a consistent header set before a new workshop season. The first email says only that the banners should look fresh. The designer turns that vague request into a short brief: identify the provider clearly, use the approved phrase Practical workshops for small teams, and prepare the agreed placements. The banner is not expected to contain the full course catalog or explain booking conditions.

Confirm which accounts and placements actually need artwork. A personal professional profile and an organization page are different deliverables even when they use the same brand name. Write the placement names into the brief and use the matching presets later. A request for every available export can create unnecessary work if the client only needs three. Completeness means fulfilling the agreed scope, not supplying a file for every possible destination.

Name the people involved. The agency designer builds the set, the client’s marketing lead collects comments, and a named owner approves the wording and identity. Another person may perform the uploads. Record those roles without assuming that the person receiving the images can also authorize a new slogan. This prevents a routine design review from becoming an untracked brand decision made by whoever happens to reply first.

Agree on the handoff contents and the review deadline. For this assignment, the client needs approved upload images, review PDFs where useful, and a matching editable JSON project for each customized placement. Add a short note explaining versions and placement differences. Confirm whether source photography should also be transferred and where it may be stored. That conversation is easier before the agency imports assets than after a recipient asks why a project includes an unexpected photo.

Collect a usable logo and a small brand reference

Ask for the approved logo rather than extracting one from a web screenshot. The useful package identifies the current mark, permitted background treatments, and any minimum-space guidance the client already follows. For the maker, request a suitable raster image in a supported format such as PNG, JPG, or WebP. A vector original can stay in the brand archive, but this editor does not accept SVG as an imported image.

A transparent PNG is often convenient for a mark that must sit on a colored background. Check it against both light and dark surfaces before assuming the transparency is clean. A pale fringe, accidental white rectangle, or tiny embedded tagline may become obvious only after placement. If the supplied version is unsuitable, ask for an approved alternative. Do not redraw or recolor the logo merely to make a draft look tidier.

Collect the exact text and accent colors as agreed values, not descriptions such as the usual blue. Northway’s reference names a dark green for principal text, white for a clean background, and a bright blue accent. The designer records their supplied color values and where each is permitted. If the palette has only been approved for print, ask the brand owner which screen equivalents to use rather than silently inventing them.

Check typography early. The maker uses system fonts, so an exact licensed brand typeface may not be available. Choose an acceptable system-font substitute with the client before presenting a polished draft, or agree that this particular asset needs another production route. Also confirm permission for any photo and remove unnecessary personal information. Browser-local editing does not make an unapproved logo, image, or substitution appropriate for the client’s public identity.

Approve the words and color roles separately

Write the intended wording in plain text before arranging it. Northway’s primary line is its name, the supporting line describes the workshops, and the small brand line is omitted because it adds no essential information. This makes copy approval straightforward. The client can correct a word without being distracted by background choices, and the designer can distinguish an approved phrase from a temporary suggestion left in an earlier email.

Decide what may be shortened in shallow placements. Practical workshops for small teams is approved for the wider composition, but the client may accept Practical team workshops for a tighter version. Those phrases are not identical, so the designer asks before substituting one. If no shorter form is approved, remove the optional supporting line or revise the layout. Making text tiny should not become the default way to preserve unreviewed copy.

Assign color roles instead of spreading every brand color everywhere. Use the dark text color for the main name, a background that keeps it readable, and the accent for one restrained detail. Test contrast where the lettering actually sits, especially over photography. An approved palette can still produce an unreadable pairing. Brand compliance describes which colors may be used; it does not automatically make every combination suitable for small text.

Keep the final banner wording in the handoff note as well as inside the image. A recipient should not have to inspect pixels to answer whether a phrase was approved. This plain-text companion also makes spelling and future revision checks easier. It is not a replacement for the native account’s text fields or a claim that lettering inside a raster image becomes selectable, searchable, or accessible as ordinary page text.

Build one reference composition, then reflow each placement

Choose a first placement that represents the main use, then build the reading order there. Northway begins with its name on the left and a simple approved mark on the right. The supporting phrase stays close enough to the name to read as one group. Before adding a photo, the designer checks whether the text-only version already solves the brief. Extra imagery should have a purpose beyond filling a quiet area.

Use the project label to identify the assignment clearly, and confirm the selected platform and placement before refining details. A familiar-looking rectangle can hide the wrong preset. The exported dimensions follow the chosen working canvas; they do not make the layout a certified native viewport. Keep the editable message guides as planning aids and leave enough room around the mark to respect both the client’s guidance and the visual composition.

Before moving to another placement, export the current image and save its matching JSON project. Then change placements and revise line breaks, supporting copy, photo fit, or layout as needed. Save another image/project pair for that version. The editor keeps one current state; selecting an earlier placement does not restore its former wording. Preserve the name, logo treatment, and color roles as the stable identity while allowing shallow headers to use simpler compositions.

Use the message-area detail view to inspect the words and mark together. It enlarges the selected box rather than simulating a device crop. Check the exported image at a smaller size separately, then review the destination platform’s actual preview. The safe area and cropping guide explains those different checks. Record intentional differences between versions so the client reviews the family as a coordinated set rather than mistaking a shorter variant for unfinished work.

Make approval refer to a specific version

Send the first review with a clear label such as Northway banner set v01, the included placements, and the questions requiring an answer. Ask for confirmation of wording, logo treatment, and composition before inviting minor polish. Include the review PDF when useful, because it can carry the artwork alongside placement and dimension notes. Explain that it is a review document rather than the file the account owner should upload.

Request consolidated comments from the named client contact. A useful note says that v01 uses the retired logo in the organization header. A vague note says the design feels off. Both can begin a conversation, but only the first immediately identifies an observable correction. Ask a clarifying question when feedback could change several different things. Guessing at the intended revision often creates another review round without resolving the original concern.

Separate required corrections from optional preferences and changes to scope. Fixing the provider’s name is a correction. Trying a different photo is a design request. Adding another platform placement is a deliverable change. Keep those categories in the review note so everyone understands what is being approved next. The designer should not quietly add a new promise to the banner because a casual comment sounded like an attractive headline.

After revising, issue v02 with a concise change summary and ask for approval of that exact set. A message saying looks good is useful only when everyone knows which files it refers to. Keep an approval record with the approver, date, version, and any exceptions. If one placement still needs work, label it pending. Do not let approval of the strongest example stand in for approval of every other exported composition.

Choose the right file for each job

PNG and JPG are the publishable artwork formats in this workflow. Start by comparing the downloaded results rather than choosing only by file extension. PNG is a useful starting point for logos, hard edges, and flat colors. JPG may be suitable for a photographic design, but inspect the name and logo for compression artifacts. Whatever the format, the artwork should contain the approved design without guide overlays, review labels, watermarks, or advertising.

Open each exported image and check the pixel dimensions, exact words, logo version, and background. Compare it with the approved review, not with your memory of the editor. A successful download confirms that a file exists, not that it is the correct deliverable. If the destination rejects the image or displays it differently, investigate the actual upload requirements and result. Avoid reducing quality or changing the composition without keeping track of the new version.

A ZIP is a delivery container, not another artwork format. The all-preset export reflows the current content across eight placements; it does not archive earlier custom drafts. Inspect every generated image and distinguish requested placements from extras. When the approved set uses different words or photo positions, deliver the separately saved images and matching JSON projects instead. Review PDFs belong with approval materials, not among the banner images selected for native upload.

Save each placement’s JSON explicitly before changing its design or closing the working session; there is no invisible autosave to rely on. Each project can include prepared embedded media, so handle it as a client asset rather than harmless settings text. Keep original high-quality media separately because those prepared copies may not replace archive originals. Give the recipient enough context to reopen the correct project without assuming a flat PNG preserves editable text and layout.

Use filenames that identify the approved artwork

A practical filename starts with the client, then states the destination, placement, dimensions, and version. For example, northway_linkedin-personal_1584x396_v03_approved.png identifies one specific export. The dimensions here describe the selected working preset, not a permanent promise about a platform specification. Use a consistent pattern across the set so the uploader can distinguish a personal header from an organization header without opening both and guessing from their shapes.

Keep version numbers stable within an approval round. If all three approved placements belong to v03, use v03 across those images even when only one changed after v02. The change summary can explain which composition was revised. Avoid names such as final-new, final-final, or latest, because they do not sort usefully and become misleading after the next correction. A simple numeric sequence remains understandable when the project is reopened months later.

Separate the approved upload images from review materials and working experiments. A handoff note can list each upload filename, its intended account placement, and whether a shorter supporting line was intentional. Keep the matching review PDF and editable project clearly named with the same version. The note should also identify who will perform the native uploads. The banner maker prepares the files; it does not change the client’s account artwork.

Ask the recipient to confirm receipt and inspect one actual uploaded result before the assignment is closed. If desktop and mobile views are relevant, check both where available. Record any display issue against the exact filename and viewing condition. Keep superseded approved exports in an archive rather than mixing them into the current upload folder. The goal is a handoff that remains clear to someone who did not attend the design review.

Handle revisions without losing the approved baseline

Three months later, Northway asks to replace workshops with short courses. The agency opens the approved JSON for each affected placement and records the wording request before editing. It does not overwrite the only v03 sources or assume the new phrase is approved because it arrived in a casual message. Save new working versions, confirm who can authorize the language, and identify whether the change affects every placement or only a temporary campaign variation.

Recheck the composition after any copy change. A slightly longer word can alter line breaks, weaken the relationship to the logo, or push text toward an uncertain edge. Revisit any shorter variants rather than mechanically replacing the same word everywhere. If the requested phrase cannot fit comfortably, present an explicit choice between approved shorter wording, a changed layout, or removal of optional copy. Keep the client involved in decisions that change meaning.

Record what remains unchanged as well as what changed. The logo, colors, and photo permission may still be valid, while the text needs another approval. For a temporary banner, agree on a replacement date and the person responsible for restoring the evergreen version. A content calendar can support that planning, but a reminder is not an automated header update. The account owner still performs the native change.

Close the revision with the same checks as the original job: review the exported images, confirm the approved version, update the handoff note, and preserve the previous baseline. Return to the banner maker when a genuine design or wording change is needed. A reliable banner workflow is not constant redesign. It is a clear chain from supplied assets and approved language to readable artwork, identifiable files, and accountable changes.

Questions about Brand Design and Export

Continue with another banner guide

Prepare the actual design in the Banner & Cover Maker, or open a related workflow below. Browse all free tools for another content task.