Why Do My Website Images Look Blurry or Broken?

VenbitThe Venbit TeamJuly 24, 20264 min read

The short answer

Blurry images almost always mean a small, low-resolution file is being stretched larger than it should be, or aggressive compression crushed the quality. A broken image, the little placeholder icon, means the file isn't there: it was deleted, moved, renamed, or the link points to the wrong place. These are two different problems with two different fixes.

Key takeaways

  • Blurry equals a low-resolution image stretched too big, or over-compression. The fix is a larger, cleaner source file.
  • A broken-image icon means the file is missing or the URL is wrong, not that the image quality is bad.
  • Retina and high-density phone screens make an image that looked fine on an old monitor suddenly look soft.
  • Uploading images at the size they'll actually display avoids both blurriness and slow loading.
  • Broken images after a site move usually trace back to a changed folder path or an unmigrated media library.

First, figure out which problem you actually have, because "blurry" and "broken" look different and get fixed differently. Blurry means the image loads but looks soft or pixelated. Broken means the image doesn't show at all, just a placeholder icon or an empty box. Here's what's behind each.

CauseHow commonThe tell
Low-resolution image stretched too largeVery commonBlurry or pixelated, worse the bigger it displays.
Over-compression by the platform or a pluginCommonBlocky, muddy detail even though the file is a decent size.
High-density (retina) screen exposing a small imageCommonLooked fine on an old monitor, soft on a modern phone or laptop.
File moved, deleted, or renamedCommonBroken-image icon. The image is simply not at the address given.
Wrong or broken image URL after a site moveCommonBroken icons appear after a migration or a domain change.
Blurry vs. broken images: what's really going on

Fixing blurry images

Blurriness is nearly always a resolution problem. The image is smaller than the space it's filling, so the browser stretches it and softens every detail. A logo saved at 200 pixels wide looks crisp at that size and mushy when it's blown up to fill a 600-pixel header.

The fix is to upload a source file at least as large as the space it displays in. Modern phones and laptops have high-density screens that pack in extra pixels, so a good rule is to use an image roughly twice the display dimensions. Displaying at 400 pixels wide? Upload an 800-pixel version. It stays sharp without being wastefully huge.

Watch out for over-compression too. Some platforms and optimization plugins squeeze images so hard to save space that they visibly degrade. If your originals are sharp but they look blocky once uploaded, dial the compression back a notch. There's a balance between file size and quality, and pushing too far toward small ruins the look. That same balance matters for speed, which our guide on mobile-only slowness gets into.

Fixing broken images

A broken image is a different animal. The quality is irrelevant, because the file isn't loading at all. The browser went looking for it at a specific address and found nothing, so it shows a placeholder. Something happened to the file or the link that points to it.

The usual causes are simple: the file was deleted from the media library, it was renamed, a folder got moved, or the link in your page points to the wrong location. Broken images that appear right after a site migration or a domain change are almost always caused by URLs still pointing at the old location or a media library that didn't come across in the move.

To fix one, check the image's link and confirm the file actually exists at that address. Re-uploading the image and re-inserting it usually clears a one-off case. When a whole batch breaks after a migration, the fix is a search-and-replace on the old paths, which is faster than fixing each image by hand.

Upload images the right size in the first place

The habit that prevents both problems is sizing images to their real display size before uploading. Too small and they blur. Way too large and they load slowly and sometimes get auto-compressed into mush. Matching the file to where it'll appear keeps images sharp and pages quick, and it saves you from re-doing this later.

If you'd rather never fuss with this again

Getting images right, correctly sized, properly compressed, and not broken after a change, is exactly the kind of small ongoing detail that's easy to let slide. We handle image and media upkeep as part of our maintenance plans, which start at $99 a month, so new photos go up at the right size and nothing quietly breaks after a migration or update.

We're based in Mill Creek, Washington, north of Seattle, and we work with businesses across the Puget Sound and remotely nationwide. If your images look rough and you'd rather someone just fix it, that's an easy one for us.

More website answers

Every question in this series, from Website Problems, Solved.

Symptoms & emergencies19
What happens if...9
Cost & pricing7
Plans & hiring10
Ownership & switching9
Platform-specific7
Seattle & local2
Venbit

The Venbit Team

Web design & SEO, Seattle

Venbit is a Seattle-area web design, SEO, and digital marketing studio. Since 2011 we've designed, built, and ranked small-business websites for clients across the Puget Sound and around the country, so the numbers and advice here come from real projects, not a content mill.

Common questions

Questions, answered straight.

Straight answers about website fixes for your business. If yours isn't here, ask us directly and we'll give it to you straight.

Ask the team

Almost always because the uploaded file is smaller than the space it displays in, so the browser stretches it and softens the detail. Upload a version at least as large as the display size, ideally about twice as large to stay sharp on high-density screens. For logos specifically, a vector file like SVG stays crisp at any size.

It means the browser couldn't find the image file at the address it was told to look. The file was likely deleted, renamed, or moved, or the link points to the wrong place. It's not a quality problem. Check that the file still exists at the linked location and re-upload or fix the path if it doesn't.

Migrations commonly leave image links pointing at the old location, or the media library doesn't fully transfer. The pages reference addresses that no longer resolve, so the images break. The fix is usually a search-and-replace to update the old paths to the new ones, plus confirming the media files actually came across in the move.

Match the image to where it'll display, then roughly double it for high-density screens. If a photo shows at 500 pixels wide, upload it around 1,000 pixels. That keeps it sharp without being wastefully large. Uploading much bigger than needed slows the page and can trigger aggressive auto-compression that hurts quality.

Free 30-minute strategy call

Let's talk about your project.

Tell us what you need and we'll give you an honest read on the project, the timeline, and what it takes, before you spend a dollar. Based in Seattle, working across the Puget Sound.

4.8 on Google 5.0 on Yelp