7 Logo Mistakes That Make a Business Look Unfinished

A client forwards you a thread. Six replies down, there's your logo in someone's email signature, sitting in a pale gray rectangle on a white background. Nobody in the thread mentions it. Nobody ever will. They just register, somewhere below the level of conscious thought, that your company is slightly less put together than the one above you in the chain.

That's what "unfinished" means in practice: not ugly, not badly drawn, just visibly assembled by someone in a hurry with whatever file was on hand.

Almost none of the failures below are design opinions. Most are checkable file problems, the kind with a specific fix rather than a debate.

1. The logo is a JPEG, so it arrives with a box

This is the most common one by a distance, and the gray rectangle in the email signature is its calling card.

JPEG has no alpha channel. There is no way for a JPEG to say "this pixel is nothing." Every pixel gets a color, so the empty space around your mark gets filled in, usually with white. If the surrounding page is pure white you might get away with it, except JPEG compression puts a faint haze of noise into large flat areas, which is exactly what makes the box read as gray rather than invisible. Put that same file on a colored slide, a dark footer, or a photo, and the box is undeniable.

Logos are close to the worst possible input for JPEG. The format was built for photographs: gradual tonal shifts, no hard edges. A logo is flat color and hard edges. Compress one and you get ringing artifacts feathering out from every letterform, the visual equivalent of a sharp sound played through a blown speaker.

The fix is to stop using JPEG for the logo anywhere, full stop. Use SVG for anything on the web, since it stays sharp at any size and usually weighs less than the PNG. Use PNG for the places that won't take SVG: email signatures, most document templates, social profile uploads. PNG vs SVG for logos goes through which one belongs where.

The ten second test: drop the file onto a bright colored background in any tool you have open. If a box appears, that file should not be in circulation.

2. It's been stretched rather than scaled

Someone dragged a side handle instead of a corner handle, and now the wordmark is 8% wider than it should be.

Most people won't consciously clock an 8% stretch. What they notice is that the logo in the header doesn't quite match the one on the business card, without being able to say why. On the web it's usually a CSS problem: both width and height are set on the image, in proportions that don't match the file. Set one and let the other be auto, or use object-fit: contain.

To check, put the header version and the original file side by side and look at a round letter. If the O in one is noticeably wider than tall compared to the other, it's been squashed.

3. There is no version that survives a dark background

Your footer is dark navy. Your logo is dark navy. On the live site it reads as a faint bruise, and it has been that way for eight months.

This one hides for a long time because most of the places you look at your own logo are white. Then someone views your newsletter in a dark mode email client, or a partner drops your mark into a black conference slide, or a print shop puts it on a navy tote bag. LinkedIn is a good illustration of how the problem stays invisible: its Page image specifications say a transparent logo will be displayed on a white background, and advise testing your logo on both light and dark because the platform shows it on both (checked on 09-Aug-2026 at LinkedIn's Page image specifications). So the file looks correct on your company page and breaks somewhere you weren't watching.

What you actually need is a small set rather than one file: the full color mark for light backgrounds, a reversed version for dark ones, a solid white knockout, and a solid black. Creating logo variations for light, dark, and transparent backgrounds covers how to export the set cleanly, and logo lockup terms explains what a knockout is if the word is new.

A reversed version is rarely the same artwork recolored. Thin strokes look thinner on dark backgrounds, because light bleeds visually into the dark around it, so a hairline that reads fine in navy on white can vanish in white on navy. The reversed version usually needs slightly more weight.

4. It turns into a smudge at 32 pixels

Open your site and look at the browser tab. If you see a gray dash, or a shape you can't identify without knowing what it's supposed to be, the favicon has failed.

A favicon.ico is normally built at 16, 32 and 48 pixels, with a 180 pixel apple-touch-icon for iOS home screens. A three word horizontal wordmark cannot survive that. Neither can a mark with a thin outline, an inner shadow, or a tagline set in 9pt. Whatever detail you love at 400 pixels is gone.

The fix is not to shrink harder. It's to have a separate icon-only mark: one letter, or the symbol from your lockup, drawn to hold up as a solid shape at 32 pixels. Favicon design walks through simplifying the mark, the favicon generator will export the sizes, and ICO vs PNG vs SVG favicons covers which file format actually renders where in 2026.

Small size trouble isn't only a browser tab problem. Google's structured data guidance for the Organization logo property requires an image of at least 112 by 112 pixels, requires that the image URL be crawlable and indexable, and warns to check that the logo reads on a white background, since a mostly white or light gray mark can disappear where Google shows it (checked on 09-Aug-2026 at Google's logo structured data documentation). Businesses regularly point that field at a 90 pixel header image and then wonder why search results show something else; Organization schema markup covers the rest of that block.

5. The logo only exists in color

Somebody asks for a one color version for an embroidered polo, and the answer is to open the full color file in Photoshop and hit desaturate.

What comes back is a mark where two shapes that were clearly separated by hue are now the same mid gray, touching, unreadable. Or a gradient that becomes a muddy band. Gradients are the usual culprit: they band in cheap CMYK printing, they lose all their separation in single color, and they cannot be done at all in embroidery, foil, vinyl cutting, engraving, or on a thermal receipt printer.

You do not get to choose which of those surfaces your logo lands on. A supplier will need it, and they will need it on a Thursday. A proper single color version is drawn, not filtered: contrast has to live in the geometry rather than in the palette. How to design a logo that works in black and white covers the test and the usual repairs.

6. Nobody ever decided how much room it needs

Four pixels of clear space in the header, none on the invoice, a bounding box centered on the trade show banner even though the mark reads heavy at the bottom. Nobody flags any single instance.

The logo in your header sits four pixels from the first nav link. On the invoice it's tight against the top edge of the page. On the trade show banner someone centered it inside its bounding box, but your mark is visually heavy at the bottom, so it reads as sitting too low. Every individual placement is defensible. Together they read as a business where nobody is in charge of the details.

Clear space is the fix, and it has to be written down somewhere in a form a non designer can follow. Pick a unit derived from the mark itself so it scales automatically: the height of the capital letter in the wordmark, or 25% of the icon's height. The rule is then "nothing enters that margin," and it holds whether the logo is 40 pixels tall in a nav bar or two meters tall on a van.

While you're there, decide which lockup goes where. Horizontal in a header, stacked in a square social avatar, icon alone at small sizes. Most inconsistency comes from someone reaching for the only file they had rather than the right one, which makes it a supply problem more than a discipline problem. What logo files a small business actually needs is the shortest list I would accept.

7. There are three of you in circulation

The website has the mark you approved last year. The invoice template in your accounting software still has the version from before you tightened the letterspacing. Instagram has a crop somebody made on their phone at a conference, because the real file wasn't in Drive and the booth opened in an hour.

Each version was a reasonable call in the moment it got made. The problem shows up when a customer sees two of them close together, which happens more than you'd think: they book on the site, get a confirmation email, then look you up on Instagram. That sequence takes ninety seconds and quietly contradicts itself twice.

The cure is boring. Make a list of every surface your logo appears on, including the ones you don't control: site header and footer, favicon, email signatures for everyone on the team, invoice and quote templates, every social profile, Google Business Profile, the app store listing, packaging, the supplier who prints your bags, the trade association directory that still has a 2022 file. Then work down it. Most people find somewhere between fifteen and thirty surfaces and are surprised by at least three of them.

Then put the real files in one place with obvious names, and send that link instead of attaching a PNG whenever someone asks. A file attached to a message today is a stray copy six months from now, with no way to tell it's not current.

Check these in ten minutes

Open your own site and one recent invoice and run this list. This tells you what's broken. Fixing it is a separate pass; write down what fails here and deal with it afterwards.

Anything that fails here is usually a missing file rather than a design flaw, one export away from being fixed rather than a reason to redesign the mark.

If you're working from a single file someone sent you once and you've been improvising ever since, Brandize generates the whole set in one pass: SVG and PNG, light, dark and mono variants, favicon sizes, and social crops. Or export them yourself from whatever tool you already have. Either way is fine, as long as it's the same file everyone reaches for next time.