Embedded HTML Images Not Displaying on eBay? Here’s Why (and How to Fix It)

Mathias Avatar

|

Last updated

eBay listings still allow HTML descriptions, but the platform’s security rules have become far stricter over the years. As a result, many sellers discover that embedded HTML images simply don’t appear, or worse, the HTML gets stripped out entirely.

This guide explains why embedded images disappear, how eBay’s template editors and filters handle HTML, which tags and attributes are blocked, and the safe, compliant ways to embed images today.

1. Why eBay Removes Embedded HTML Images

When you add images using HTML (<img src="...">) inside the description, eBay often strips, rewrites, or blocks them. That’s because:

▶️ Inline images are considered a security risk

Embedded HTML can trigger:

  • Cross-site scripting (XSS)
  • Cookie/session hijacking attempts
  • Browser redirects
  • Slow or malicious remote content

To protect buyers, eBay sanitizes every description with automated security filters.

▶️ Remote calls to external servers are heavily restricted

An <img> tag loads content from another domain. If the domain:

  • uses redirects
  • is served over http
  • responds slowly
  • is unknown or flagged
  • returns non-image MIME headers

…then eBay may silently strip the tag.

▶️ Legacy HTML is no longer allowed

Old templates often contain:

  • <iframe>
  • <script>
  • <embed>
  • <object>
  • <style> in certain contexts
  • javascript: links
  • Event handlers like onclick

If these appear anywhere in the description, eBay may remove nearby <img> tags because the entire block is sanitized.

2. Template Editors Often Break Embedded HTML

Most sellers copy/paste HTML from:

  • A purchased template
  • A third-party editor
  • A Word document converted to HTML
  • A design tool like Canva or Stripo

But eBay’s listing form and business policies editor use an HTML parser that auto-cleans:

What gets removed automatically:

  • Inline CSS that is not in the safe list
  • <img> tags that include forbidden attributes (ex. onload=, position:absolute)
  • DOM elements nested improperly
  • Code copied from WYSIWYG editors that includes <span> or <div> wrappers eBay flags

Worst-case scenario

The editor “cleans” your code twice:

  1. Once in the WYSIWYG panel
  2. Again when saving to eBay’s servers

This is why an image may appear in the editor, then vanish after pressing Publish.

3. Blocked or Rewritten HTML Tags

Here are the most common reasons an image tag gets blocked:

1. Unsafe attributes

eBay strips:

  • style="position: absolute; top: …"
  • onload=
  • onclick=
  • background-image:
  • data: URLs

If your template generator uses these, images nearby may be removed.

2. Tags inside a forbidden parent

If your image is inside:

  • <iframe>
  • <script>
  • <noscript>
  • <object>
  • <marquee>

…it won’t survive the sanitization.

3. Poorly formed HTML

Missing:

  • closing tags
  • correct nesting
  • valid HTML5 structure

eBay’s parser simply discards invalid sections instead of fixing them.

4. Why Inline Images Get Stripped Even When They Look Safe

Even a simple <img src=""> tag can disappear because eBay performs:

A. HTTP security checks

eBay may block images that:

  • load via http:// instead of https://
  • redirect through multiple URLs
  • require cookies or authentication
  • return incorrect MIME headers (e.g., text/html instead of image/jpeg)

B. Content Safety Scanners

eBay uses automated tools to detect:

  • hidden tracking pixels
  • invisible 1×1 images
  • embedded affiliate trackers
  • scripts loaded via src=

Any image suspiciously small or from a questionable domain may be filtered.

C. Domain Reputation

New domains, personal servers, hosting providers with spam histories, or dynamic URLs often fail the trust checks.

5. Remote Image Calls: How eBay Handles External Sources

Remote image URLs must:

  • Be direct image files ending with .jpg, .jpeg, .png, or .gif
  • Respond with fast CDN speeds
  • Serve content through HTTPS
  • Use a stable, unchanging URL
  • Return a clean Content-Type: image/* header
  • Avoid redirects and tracking parameters
  • Come from a well-known, safe hosting provider

CDNs that heavily rewrite URLs or generate temporary URLs can break embedded images.

6. How to Embed HTML Images Safely on eBay

You can still embed images in descriptions… you just need to do it the way eBay expects.

✅ Use only safe HTML

Allowed tags:

<img src="https://yourcdn.com/image.jpg" alt="" border="0">

Safe attributes:

  • src
  • alt
  • width / height (optional)
  • border

Avoid all inline CSS except simple sizing.

Use a compliant, stable hosting provider

Your image URLs should be:

  • Direct file links
  • Permanent (unchanged over time)
  • CDN-accelerated
  • Redirect-free
  • HTTPS only
  • Returning proper MIME types
  • Lightweight and fast

(Img.vision is designed exactly for this use case, ensuring URLs always load safely inside eBay descriptions.)

Avoid template generators that inject risky code

Use editors that produce clean HTML5.

Avoid:

  • Word → HTML conversions
  • “Free eBay templates” containing invalid or outdated code
  • Builders that embed scripts, animations, or CSS blocks

Validate your HTML before publishing

Use a validator like W3C HTML Validator to ensure your code is clean and properly nested.

Keep your description simple

The more complex the template, the more likely eBay will strip sections. Minimal HTML = maximum reliability.

7. When You Should NOT Embed HTML Images

Avoid embedding if your use case is:

  • Primary product photos
  • Gallery or thumbnail images
  • Variations (color, size)
  • Mobile-first listings

For these, always use eBay’s photo uploader.

HTML images are only appropriate for:

  • Size charts
  • Shipping diagrams
  • Warranty badges
  • Instructional images
  • Infographics

…as long as they follow safe HTML rules.

Conclusion

If your embedded HTML images aren’t showing on eBay, it’s almost always because of one of the following:

  • Template editor strips unsupported tags
  • eBay’s security filters remove risky HTML
  • Inline images contain blocked attributes
  • Remote image calls fail safety checks
  • The hosting domain is redirecting, insecure, or not compliant

Follow the safe-HTML guidelines above, keep templates simple, use a clean and trusted CDN, and your embedded images will display reliably every time.


Mathias Avatar

Last updated