Complete workflow

How to audit a logo folder before handoff or migration

A good folder audit connects visual comparison, production checks and documented decisions. It should make the next designer faster, not merely make the directory look tidy.

OutcomeAn approved master, a controlled variant set and an evidence-backed cleanup plan.

Workflow guide. The private comparison tool accepts one master and up to 60 selected reference images from files, a folder or ZIP. Optional saved fingerprints stay in your browser. Export JSON, CSV or a print review; no files are changed or deleted.

1. Preserve the intake state

Work on a copy or create an inventory before renaming anything. Record filenames, paths, formats and dimensions. A cleanup without an audit trail can destroy useful provenance.

2. Confirm ownership and permission

Only analyze files your team owns or is authorized to process. Separate third-party reference marks from deliverable client assets. Do not convert a private folder audit into a public logo database.

3. Designate the approved master

Identify the current primary mark and its official geometry, colors and spacing. If approval is disputed, document the uncertainty and request a decision from the responsible stakeholder.

4. Compare the working set

Compare each reference with the master, then inspect relationships among references manually. The local tool compares one master against up to 60 files; it does not cluster a whole folder. Similarity narrows the queue; it does not replace checking original vector paths, text, color values and intended use.

5. Run production preflight

  • Transparent and solid-background versions are intentional.
  • SVG and raster exports open correctly.
  • Small-size versions retain recognizable detail.
  • Palette values match the current guide.
  • Favicon and social packages use the approved mark.
  • Filenames communicate role, color and format.

6. Export decisions

Deliver a report listing the approved master, merge candidates, review items, retained variants and unresolved questions. Keep deletion as a separate, reversible action after approval.

Optional usage measurement

Help us understand which catalogues and file formats are useful. We do not record search text, uploaded images, names, email addresses or IP addresses in usage events. Events expire after 30 days. Local, staff and recognised bot traffic is separate.

Measurement is off until you opt in. Downloads have separate operational delivery counts.