Contents
  1. What a logo redesign review actually decides
  2. What you need before you start
  3. How to review and test the redesign
  4. Path, type and export settings to confirm
  5. How to confirm the result
  6. What this review cannot settle on its own

What a logo redesign review actually decides

Reviewing a logo redesign online means judging the new mark as usable artwork, not as a thumbnail on a webpage. You compare it with the current logo, place it in the sizes, colours and backgrounds it must survive, and inspect how it is built so you can accept the file, request specific changes or keep the existing mark.

A vector logo is drawn with paths: outlines made of points and curves, then filled or stroked. Paths scale without the blocky edges of a raster (pixel) image. Live type is lettering still tied to a font file. Outlines, also called curves, are those letterforms converted to paths so the mark no longer depends on that font being installed. An online preview, a mockup and a file suffix such as .ai, .eps or .svg do not prove the artwork is true vector, fully editable or cleared for reuse.

What you need before you start

  • The current logo and the proposed redesign as inspectable files, not only screenshots.
  • A short list of real placements that apply to this job, such as a site header, app icon, social avatar, print piece or signage.
  • Any documented brand rules that already exist for this mark: colour values, clear space, minimum size, one-colour versions or file formats named in the brief or guidelines.
  • Permission to use both marks in the test. A downloadable file is not a licence.
  • A way to inspect geometry, colour mode and type status, or a reviewer who can. A flattened picture in a browser tester cannot finish that job.

How to review and test the redesign

  • 1. Write down the placements and the smallest size the mark must remain readable. If the brief does not name a size, treat that as a gap and test at the smallest size you actually use, then record that size in the review notes.
  • 2. Open the source file you would edit later and the exports you would publish. Treat each file as unknown until you inspect it; the extension is not proof of vector-only content.
  • 3. View old and new side by side at the same size, on the same background, so changes in weight, proportion and recognition are visible rather than guessed from isolated mockups.
  • 4. Reduce the mark to the smallest listed size and enlarge it to a large lockup. Fail it if thin strokes collapse, counters (the enclosed spaces in letters such as a, e and o) fill in, or the wordmark becomes illegible.
  • 5. Place colour, black and single-colour versions, if they exist, on light, dark and busy backgrounds. Fail a version that disappears, vibrates against the field or relies on a drop shadow that will not be present in real use.
  • 6. Use an online mockup or tester only as a recognition check in context. Many testers show a rasterised picture; that picture can hide open paths, missing fonts and the wrong colour mode.
  • 7. Inspect path construction: extra points, open paths that should be closed, overlapping shapes that fight at small sizes, stray objects off the artboard, and strokes that still need expanding if the delivery requires filled outlines.
  • 8. Inspect type: spacing between letters, optical alignment of the wordmark with any symbol, mixed live type and outlines, and whether a font licence is still required to open or edit the file.
  • 9. Check colour against what the job documents. If the brief names RGB, CMYK or spot (named ink) colour, the file must match that specification. Do not assume a default from how the mark looks on a monitor.
  • 10. Check export: the artboard or viewBox cropped to the mark or to documented clear space, no hidden leftovers, consistent file names, and raster exports only where a pixel format is required, at the pixel dimensions the destination asks for.
  • 11. Record pass or fail against those checks. Accept the redesign, send a revision list tied to the failed checks, or keep the current logo.

Path, type and export settings to confirm

Path quality is the difference between a mark you can still edit and a picture that only looks sharp at one size. Closed, economical outlines with a single, consistent construction (for example all fills, or strokes expanded where the delivery requires it) survive scaling and colour holds. Compound paths should punch counters cleanly. Do not expand, outline or flatten the source unless the delivery asks for it; keep an editable master and make those conversions in a copy.

Typography handling depends on who will open the file next. If the next person must change the name or tagline, keep live type and supply the font files only when you have the right to do so. If the next person must place the mark without the font, convert a copy to outlines and confirm no characters dropped. Mixed live type and outlines in one lockup is a common failure: one line reflows, the other does not.

Export settings belong to the destination, not to the tester. A web placement typically needs an RGB vector or a raster at the pixel size requested by that placement. Print typically needs the colour mode named in the job, fonts outlined or embedded as specified, and bleeds or clear space only when those are documented. If the application, menu command or version matters, verify those controls in the product you use; this guide does not name a tool or a version-specific setting.

How to confirm the result

  • The redesign stays recognisable next to the current logo at the sizes you listed.
  • It remains legible at the smallest size in the review notes, in colour and in one colour where those versions exist.
  • Paths open as editable outlines without surprise gaps, extra points or objects outside the crop.
  • Type is outlined with no missing-font warning, or live type opens with the fonts and licence you actually hold.
  • Colour mode and file format match the documented delivery, not a guess from the suffix or from a mockup.
  • You can repeat the same result from the files in hand. A screenshot of an online tester is not the deliverable.

What this review cannot settle on its own

This process does not name a specific online tester, browser or design application, and it does not give menu paths or version-specific commands; those must be verified in the tool you use. It also cannot settle legal clearance, trademark conflict or contrast against an accessibility standard unless that standard is in the brief. Minimum sizes, clear-space rules and colour values are requirements only when they are written in your guidelines or job spec. If those figures are missing, record the sizes and backgrounds you actually tested and treat the undocumented rules as open items rather than implied facts.