← Back to Blog

Edge Drop Guides | Jun 26, 2026 | 8 min read

Starting a Project? How to Stage Logos, Fonts, and Briefs

By Deepender Yadav

Starting a Project? How to Stage Logos, Fonts, and Briefs — Edge Drop Guide

Kickoff is when the junk drawer starts. The brief is in email. The logo is in a zip. The typeface is a .woff2 in a shared drive. Someone copies the PNG “for now.” Now lasts three months.

This playbook is a kickoff ritual: stage a week’s kit, not a career’s archive. Pin only what Windows can honestly hold. Put files where files belong. Wipe the kit when the work ships.

Windows clipboard history holds 25 items, 4 MB each, as text, HTML, or bitmap. Unpinned items vanish at restart. Pins stay until deleted. Files — including font files and brand PDFs — are not a first-class history type. History will not become a foundry.

What Windows will hold on day one

Kickoff itemWin+VBetter home
Brief URLText card; pin if publicProject doc
Hex listText cardDesign tokens file
Logo PNG under 4 MBBitmap cardBrand folder
Logo SVGSometimes as text; unreliableBrand folder
Font filesNo (file list, not history)OS install + repo
Brand PDFNoDrive / DAM
Slack channel nameTextThe SOP
Figma file URLTextBookmark + project doc
Contract / MSANo, and should notLegal / finance store

Microsoft: 25 items, 4 MB, text/HTML/bitmap, restart wipe except pins. Fonts and PDFs are files.

How to keep font files with the specimen image is the longer pairing rule. At kickoff, install the licensed fonts and keep the specimen in the brand folder. Do not pin a screenshot of the typeface and call it the font.

Brand guidelines PDFs do not belong in history. A 30-page PDF will not appear as a reusable card. Bookmark it.

The kickoff hour

1. Create the real kit folder

P:\Clients\Acme\2026-rebrand\kit\

  • logo/ (SVG + PNG at 1x/2x if needed)
  • type/ (license + install notes; not a junk pile of every cut)
  • brief.pdf or a link document
  • tokens.txt (hex, type sizes)

This folder is the archive bucket. Three-bucket model: history is ephemeral, a pin is a weak same-week hold, the folder is the archive.

Name files boringly: acme-mark-color.svg, not logo-final-FINAL-use-this.png. The first bad name on the Desktop will be the one that gets pasted in week six.

2. Snap the folder next to the working app

Reducing Alt-Tab. The folder is the staging surface for files. Windows Snap or a second monitor is enough. FancyZones is optional.

Do not leave the zip on the Desktop as the working kit. Extract once into kit\, then archive or delete the zip so nobody opens v1 after v2 arrives.

3. Load a tiny clipboard set

Copy, in order:

  1. The brief URL
  2. The tokens text
  3. One logo PNG under 4 MB if the first day is mockups in chat

Pin 1 and 2 only if they are not confidential. Many briefs are confidential. Then do not pin. Keep the URL in the browser’s project bookmark folder instead.

A hex list is fine as text. A screenshot of the brand PDF’s color page is a worse hex list: it cannot be pasted into a tokens file, and it may exceed 4 MB.

4. Install fonts properly

Windows Settings > Personalization > Fonts, or the vendor’s installer. Figma needs the desktop font install helper to see local fonts in the browser or desktop app. That is not a clipboard step.

Licensing: install only the cuts the contract covers. A whole foundry folder copied “so it is handy” is how an unused display face ends up in a shipped deck. Keep the license PDF next to the fonts in type\, not in history.

5. Agree the paste rules

Write them in the handover SOP:

  • Slack gets compressed images. Do not treat a Slack logo as the master. Avoiding compressed chat images.
  • Figma: drop the SVG or use Copy as SVG between tools. Figma: copy assets between design tools.
  • Photoshop: Place the file; do not paste a crushed PNG from chat. Best clipboard setup for Photoshop users.
  • Outlook: Keep Text Only for the brief excerpt; attach the PDF.
  • Explorers and DAM downloads: copy the file, not a preview bitmap.

What not to stage on the clipboard

  • The entire brand zip as an Explorer copy “so it is handy”
  • Client credentials for the DAM
  • Last year’s logo “in case they change their mind”
  • A scan of the contract
  • A customer screenshot from the last project that “might be a style reference”
  • API keys, preview-environment passwords, or CMS logins

Those items either will not appear in Win+V or should not. Credentials belong in the password manager. Is copying a password ever a good idea?.

Week one versus week six

Week one: a small pinned set is a kindness. Week six: that set is folklore. Run the weekly pin review. If the logo changed, delete the old bitmap so it cannot be pasted into a deck the night before launch.

When the project ships, run the end-of-project wipe. The kit folder stays in the archive. The clipboard does not.

A mid-project rebrand (new wordmark, new hex) is a mini-kickoff: replace files in kit\, delete the old bitmap from history and from any shelf, post one message with the new path. Do not leave both marks pinned “until we decide.”

Multi-app kickoff (Figma + PS + Illustrator)

Vectors rarely survive a tour through Windows history. Figma’s own advice is SVG for interchange. Illustrator’s clipboard preferences (PDF and AICB) change what Photoshop receives; Adobe documents those switches. They do not change what Win+V stores. A history card is still a bitmap or some HTML/text, not a live .ai object.

On kickoff day, decide the source of truth:

  • UI: Figma file
  • Raster: PSDs in the repo or DAM
  • Wordmark: AI/SVG in logo/

Copy from the source of truth, not from a history thumbnail.

Sketch is not a Windows app. If the incoming kit is .sketch, import into Figma or export SVG on a Mac. Do not expect a Windows clipboard to interpret Sketch pasteboard data. Adobe XD, Figma, and Sketch on Windows.

Canva and Photopea have their own paste limits. Canva, Photopea, and browser editors. Kickoff day is a bad time to discover that a browser editor accepted a bitmap and discarded the SVG.

Color tokens on day one

Put hex (and, if the brand uses them, RGB / CMYK / PMS) in tokens.txt or the design-token file the engineering team already has. Color palettes: hex lists vs visual swatches. A pin of #0B1F3A is acceptable for the week. A pin of a screenshot of the guidelines page is not.

How to grab a color hex and keep it if the incoming kit is “a PNG of the old site.” Convert to text on day one.

Optional shelf

A hover shelf is a comfortable home for this week’s logos as tiles. That is staging, not DAM.

Edge-Drop is optional if the first week is heavy drag-into-Figma / drag-into-PS. Load the week’s PNGs and SVGs, empty it at ship. It is not a substitute for kit\ and it should not hold font files as the only licensed copies.

Keeping brand assets off the desktop and on a shelf is the ongoing version of this kickoff step. The Desktop is not a DAM.

Eagle, Billfish, and other asset managers are the right tool when the library is hundreds of files. Eagle, Billfish, and asset managers vs clip history. Do not pretend 25 history slots will do that job.

Kickoff anti-patterns

  • Desktop icons named logo-final-final.png. That is not staging. That is a landfill that will be pasted by mistake in week six. Put masters in kit\ with boring names.
  • Pinning the whole brief. A 4 MB HTML copy of a Google Doc may miss history entirely. Bookmark the doc.
  • Copying the font file in Explorer and expecting Win+V. Files are not history cards. Install the font.
  • Slack as the kit. The first PNG in the channel will be the one that gets reused, even after the brand updates. Slack compresses. The folder does not.
  • Pinning client UI from production. Unreleased screens are client assets. They belong in the project folder, not in a panel that opens during the next unrelated call.
  • Using the clipboard as the project to-do list. “Send the kickoff recap” is a task. Stop using the clipboard as your to-do list.

First-week communication

Send one message to the team (wiki, not only chat):

  • Path to kit\
  • Figma/PS source of truth
  • “Do not pin client UI”
  • Link to the wipe checklist so close-out is expected
  • Who owns font licensing questions

That message is the archive of the kickoff. History is not.

A sensible daily copy-paste workflow takes over after the hour: capture from kit\, stage only what the next paste needs, clear at the end of the day. Using filters if a third-party manager is in play — text versus images versus files as a habit, not a weekend project.

Worked kickoff: a one-hour rebrand

  1. Create kit\ with logo\, type\, brief.pdf, tokens.txt.
  2. Install two licensed weights. Confirm they appear in Figma after the font helper is running.
  3. Bookmark the brief. Do not pin it; the brief is confidential.
  4. Copy the hex list into tokens.txt. Pin the hex list on a personal workstation only if it is public brand color.
  5. Place acme-mark-color.svg into the Figma library file. Do not paste a Slack PNG.
  6. Post the wiki message with the path and the wipe link.
  7. Clear unpinned history so the DAM password from the download step is gone.

Day two starts from kit\, not from memory of yesterday’s Win+V. That is a kickoff that will still make sense at ship.

Related reading

Sources

Deepender Yadav
Written by Deepender Yadav · Author & Developer

Deepender Yadav is a B.Tech Computer Science Engineering student and software developer interested in building practical software and open-source projects.

GitHub · LinkedIn

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support

Free · Lightweight · Privacy First
Find us on CodeHype