A logo doesn't have to be expensive to look expensive, and it doesn't have to be cheap to look cheap. Price has almost nothing to do with it. What actually gives a logo away is a specific, repeatable set of visual mistakes, and once you know what they are, you'll start spotting them everywhere: on business cards, app icons, and the "final" file a freelancer just sent over.

Most people can't name what's wrong with a bad logo. They just feel it. This post is the opposite of that feeling: eight concrete, nameable tells that separate a well-made mark from a rushed one, and why each one keeps happening, so you can catch it in the proof stage instead of after it's already printed on a thousand boxes.

The Wordmark Tells: Kerning and Letter-Spacing

If a logo is built around text, the first thing a trained eye checks is the space between the letters, not the letters themselves. Kerning adjusts the space between individual letter pairs; tracking is the overall spacing across the word. Default software settings get you maybe 70% of the way there. The last 30%, tightening the gap where a capital A meets a V, opening it slightly where two straight-sided letters collide, is manual work, and it's the work that gets skipped first when a project is rushed.

You'll see it as gaps that look randomly wide in one spot and cramped in another, or a word that reads as slightly "off" without you being able to say exactly why. That unevenness is the tell. A properly kerned wordmark reads as a single, balanced shape at a glance. A poorly kerned one makes your eye stop and re-scan, even if you never consciously register that it's a spacing problem.

This happens because kerning a wordmark by hand takes real time, and it's invisible time, nobody can see the effort in the final file, only the absence of the problem. On a rushed timeline or a flat-fee job with no room for a dedicated typography pass, it's one of the first things left undone.

Default Fonts, Straight Out of the Box

The second tell shows up before you even register the spacing: the typeface itself. There's a small handful of free or near-free fonts that show up on an enormous share of new logos, the same two or three "modern and clean" geometric sans choices, used with zero customization. Nothing about the letterforms has been adjusted. It's the font, used exactly as it was downloaded.

That's a real problem for a logo, because its whole job is to be recognizable and singular to one brand. A font a hundred other companies are also using straight out of the box works directly against that goal. You end up with a mark that's legible and clean, and completely interchangeable with a dozen others you scrolled past this month.

This tell traces back to scope, not skill. Custom letterform work takes a type-focused pass that a lot of quick-turnaround logo jobs never include in the brief. A freelancer working from a template library, or a generator recombining a shape and a stock font, isn't going to produce something custom, because customization was never part of what was paid for.

Low-Resolution and Pixelated Exports

This one is less about design taste and more about basic technical execution, and it's often the fastest way to spot a rushed job. A logo should exist as a vector file first: mathematically drawn shapes that scale to any size, from a favicon to a billboard, without losing a single edge. If the only file you ever received is a JPG or a PNG that starts looking blurry or pixelated the moment you enlarge it, no vector master was ever built. What you have is a picture of a logo, not the logo.

This is a bigger deal than it looks. A vector-less logo can't be resized cleanly for a sign, cut for embroidery, or handed to a print shop without someone re-drawing it from scratch. You'll hit this wall the first time you try to do anything beyond posting the file online at the size it was delivered.

It happens because some designers, working purely in raster-based software, never produce a true vector file at all. Combine that with a rushed handoff where nobody asks for source files, and a client can go months without knowing their "logo" is just an image of one.

No Clear-Space or Minimum-Size Rules

A well-made logo comes with two invisible rules baked into how it was designed: a minimum clear-space zone around it so it never gets crowded, and a minimum size below which it simply shouldn't be used, because detail starts disappearing. Neither rule is visible in a single hero-sized image on a homepage. You only find out they're missing when the mark gets shrunk to a favicon or app icon and the fine detail turns into a smudge.

This is one of the most common ways a logo fails in the real world, because so much of where a logo actually lives today is small: a browser tab, a WhatsApp profile, an app grid icon. If nobody tested the mark at those sizes, you won't find out it breaks until it's already live somewhere you can't easily fix.

The root cause is almost always a missing deliverable, not a design flaw in isolation. A single final file with no size variants, no favicon-specific simplified version, and no written guidelines document means nobody defined the rules in the first place, because nobody built a system, they built one image. If you're not sure what should be included in a complete logo handoff, our packages page lists exactly what comes with each tier, guidelines, variants, and all.

Inconsistent Line Weights in Icon Marks

For logos built around an icon or symbol rather than pure type, the equivalent of bad kerning is inconsistent line weight. Look closely at the strokes: are they the same thickness all the way around, or does it randomly thin out in one spot and thicken in another? Skilled icon design involves optical correction, subtly thickening a stroke where it curves, because a perfectly uniform mathematical stroke can look thinner at the curves to the human eye. Getting that right takes a trained pass. Getting it wrong looks like a shape drawn freehand and left as the first draft.

The effect reads as unsteady or amateur even to someone who couldn't explain why. Your eye picks up on the wobble in a way that undermines trust in the mark, the same way an unevenly drawn circle looks "off" before you could ever name the geometry.

This tell almost always comes from skipping a construction grid, the underlying geometric guide that keeps every curve and angle consistent, combined with a process that never included a second look. First draft becomes final draft when there's no built-in revision round to catch it.

Drop Shadows, Bevels, and Gradients Used as a Crutch

Effects aren't the enemy here. Plenty of strong, contemporary logos use a gradient or subtle depth intentionally, as a deliberate choice layered onto a shape that already works. The tell isn't the presence of an effect, it's when the effect is doing the work the shape should be doing on its own. A heavy drop shadow, an embossed bevel, or a glossy gradient dropped over a flat, weak, or generic shape is often there to manufacture a sense of "premium" or "polished" that the underlying form doesn't actually earn.

The test is simple: strip every effect away and look at the mark as one flat, solid color. If it still reads clearly and holds together as a shape, the effects on top are a stylistic choice. If it suddenly looks thin, generic, or barely there without the shadow propping it up, the effects were doing structural work they were never meant to do. That flat-color test is a standard part of how we approach every brand identity project before a mark is ever signed off.

This happens because testing a mark as a flat, solid form is a specific proofing step, and it gets skipped when a project moves fast. It's much quicker to add a gradient and call it finished than to go back and strengthen a shape that isn't pulling its weight.

A Mark That Only Works on One Background

A logo that looks great on white and falls apart everywhere else usually only exists as one file, tested in one context. The real test is whether it holds up reversed out of a dark background, dropped onto your brand's own accent color, or printed in a single flat color with no gradients available. If nobody has produced and checked a white-on-transparent version and a single-color knockout, you don't actually have a finished logo. You have a picture of one, on white.

You'll usually discover this problem at the worst possible moment: building a dark-mode app icon, ordering merchandise in a single ink color, or dropping the logo onto a colored ad template and watching it disappear. A logo that was properly tested handles all of that because someone thought it through before handoff, not after.

It happens for the same reason the clear-space rules go missing: a rushed process that delivers one final file instead of a small system of variants, because building out reversed and single-color versions is additional work that a quick, low-cost job usually never scopes in.

Generic, Stock-Clipart-Style Icons

The last tell is the easiest to spot once you're looking for it: an icon that feels instantly familiar, even though you've never seen this specific business before. A generic swoosh, an abstract leaf that could belong to any wellness brand, a laurel wreath, three overlapping circles. These shapes are the base building blocks in stock icon libraries and AI logo generator tools, and when a mark is assembled by recombining them instead of being drawn from scratch for one brand, it shows.

The giveaway isn't that the icon looks bad in isolation, it's that it feels borrowed. It doesn't reflect anything specific about the business it represents, because it wasn't built from that business's story, it was pulled from a shelf of shapes that fit any business.

This one comes down to whether real concept development ever happened. A custom mark starts with research into what the brand actually does and who it's for, several rough directions, and a chosen concept refined over rounds of feedback. Skip that process, and a stock shape with a font next to it is what fills the gap instead. It's the exact gap our brand identity process is built to close, concept work first, execution second.

TellWhat Causes It
Uneven letter-spacing in the wordmarkNo manual kerning pass; default tracking left untouched
Off-the-shelf font, zero customizationTemplate used as-is; no custom type work in scope
Blurry or pixelated logo filesNo vector master ever built; raster export delivered as "final"
Mark breaks apart at favicon sizeNo minimum-size testing; no brand guidelines document
Uneven stroke weights in the iconNo construction grid; first draft shipped without revision
Heavy gradients, bevels, or shadowsWeak flat form; effects used to fake depth and quality
Logo only works on whiteNo reversed or knockout version ever tested
Generic clipart-style iconStock asset or AI generator output; no custom concept work
"A well-made logo survives being shrunk to 16 pixels, printed in one flat color, and stripped of every effect. If it only works at full size, in full color, on a white background, it was never actually finished."

Want a logo built on actual design fundamentals?

No default fonts, no guessing at kerning, no single white-background file. Every logo we build is tested at favicon size, in one color, and on your actual brand colors before you ever see a final version.

See Our Brand Identity Process →

Frequently Asked Questions

What makes a logo look cheap even if it wasn't cheap to make?

It's rarely about the price paid. It's specific execution mistakes: uneven kerning, a default font used with zero customization, low-resolution exports, missing clear-space rules, and a mark that was only ever tested on a white background. Any one of these can make an expensive logo read as cheap, and skipping all of them is what separates a well-made mark from a rushed one, regardless of budget.

How can I tell if a logo will hold up at small sizes like a favicon?

Shrink it down to 16x16 or 32x32 pixels, actual favicon size, and look at it at that size, not zoomed in. If fine details, thin strokes, or small text disappear into a smudge, the mark wasn't designed with a minimum-size rule in mind. A well-built logo has a simplified version specifically for small use cases like favicons and app icons.

Is a logo with a gradient or drop shadow automatically bad?

No. Plenty of strong logos use a gradient or subtle depth deliberately, on top of a shape that already works on its own. The problem is when the effect is covering for a weak or generic shape underneath. Strip the gradient or shadow away and look at the mark as one flat, solid color: if it still holds up, the effect is a style choice. If it falls apart, the effect was doing work the design should have done.

What's the fastest way to check if a logo design is actually well-made?

Run three quick tests before you approve anything: shrink it to favicon size, view it as a single flat color with no effects, and place it on at least one dark or colored background instead of white. A logo that holds up in all three was actually tested and finished. One that only looks good at full size, in full color, on white was never fully executed.

None of these tells require a design degree to spot, they just require knowing what to look for before you approve a proof instead of after it's already printed, embroidered, or live on your app icon. Price was never the reliable signal. Execution is, and now you know exactly what to check for it.