Worst Logo Changes: How to Evaluate Failed Redesigns

Before you start

This guide is about evaluating failed logo redesigns, not about running a specific app or service. You can complete the process locally using screenshots, exported image files, and the Logo Lab tools in this site. No account or upload service is required unless your workflow includes one.

Prepare the old and new logo files in a format you can open locally, such as PNG or SVG. Also prepare a neutral background, a small-size test export, and a short list of places where the logo will appear: profile image, website header, printed sign, and app icon are enough for most evaluations.

Step-by-step instructions

1. Compare what the old mark communicated

Start by listing the elements people already recognized in the previous logo: shape, initials, symbol, spacing, and the most common background color. Do not judge whether the old logo was attractive. Judge what it reliably identified. If the new design keeps the same core shape or initials, the change is easier for viewers to understand. If it replaces all of those elements at once, the redesign has a higher risk of breaking recognition.

2. Check contrast on light and dark surfaces

Place the new logo on plain white and plain near-black backgrounds. Look for details that disappear, especially thin lines, small lettering, or a dark mark placed on a dark photograph. Use the Palette & Contrast tool to enter the main foreground color and the background color, then check whether the contrast ratio supports normal-sized text. A redesign can fail even when it looks good in a presentation if the main mark cannot separate from common real-world surfaces.

3. Test the smallest real size

Export or resize the new logo to 32 pixels, 24 pixels, and 16 pixels in height. At the two smaller sizes, look for parts that merge into a speck or become unreadable. Faded gradients, very thin strokes, and long wordmarks are the most common failures. If a symbol remains recognizable at 24 pixels, it is likely to survive as a favicon or mobile interface element.

4. Review the redesign against a narrow use case

Do not evaluate the redesign as a single standalone image only. Test it in one practical context: a browser tab, a printed card, or a storefront sign mockup. A logo can pass a large presentation slide and still fail as a tiny social avatar because the letter spacing closes up or the mark becomes too complex.

5. Name the concrete losses instead of saying it feels worse

Write down the specific failures: "contrast drops below the AA mark," "the wordmark loses legibility below 24 pixels," "the new mark duplicates a common generic shape," or "the palette adds a color that is absent from the existing brand system." Specific loss statements make it easier to decide whether the problem should be corrected or whether the new version should be rejected.

Check the output

A successful evaluation produces a short, verifiable list of failures rather than a general preference. Confirm that you have compared the old and new marks under the same size and background conditions, checked the main color pair for accessible contrast, and tested at least one small reproduction size. Do not claim a redesign is objectively worse only from personal taste; support each failure with the observable condition that caused it.

Common problems and next steps

The new logo looks clean but people cannot find the brand

If the new mark removes the recognizable shape and replaces the wordmark with an abstract symbol, treat recognition as the main problem, not aesthetics. The next step is to restore one familiar element: keep the old symbol shape with new typography, or keep the old wordmark structure with a simplified mark.

The symbol is fine at full size but disappears when small

Reduce the number of thin details, increase spacing inside the mark, and test again at 24 pixels. If necessary, create a separate compact symbol rather than shrinking the full logo. This is a common correction for app icons and favicons.

The color palette looks modern but fails on photos or dark headers

Define the light and dark background versions separately. If the main version depends on a very light background, do not force it onto dark surfaces. Check the contrast pair again with the actual foreground color used in the exported file.

The redesign changed too many elements at once

Roll back the change to a staged version. Test a revision that alters only the mark, only the typography, or only the color system. Staged testing shows which element caused audience confusion and prevents discarding a useful direction because of one weak part.

How to use Logo Lab while comparing redesigns

Load the old and new versions into the Before/After slider for direct visual comparison. Use Mockup Preview to place both versions on a sign, card, or screen scene. Run Palette & Contrast on the foreground and background pair, and use Resize & Convert to produce the small test sizes. The tools help you document the failure, but the decision still depends on the brand recognition and use-case checks above.