A surprising number of eBay listings in 2026 are still wrapped in templates designed a decade ago — JavaScript widgets, HTTP-hosted images, fixed-width table layouts. Some of these listings render badly. Some get their descriptions partially hidden by eBay. And since June 1, 2026, a whole generation of InkFrog-built templates stopped rendering at all when that service shut down.
This guide covers what an eBay listing template is actually allowed to do in 2026, why old templates break or get suppressed, and how to test yours before eBay or your buyers do it for you.
The active content ban: no JavaScript in eBay descriptions
The foundational rule, in force since 2017: eBay does not allow active content in listing descriptions. Active content means JavaScript, Flash, plug-ins, and form actions — anything that executes rather than just displays.
That killed an entire era of template features: image sliders and carousels driven by scripts, hover-zoom widgets, animated countdown timers, embedded video players that relied on plug-ins, cross-promotion galleries that fetched your other listings, and visitor counters. eBay blocks or strips active content rather than running it, so a template that depends on a script doesn't degrade gracefully — the feature simply doesn't work, and often leaves broken markup behind.
What you're left with — and it's enough — is HTML and CSS. Static layout, styled text, images, links. A compliant 2026 template is closer to a well-formatted document than an app.
The practical test: view your description's source and search for <script, onclick=, onload=, or any javascript: URL. Any hit means the template is non-compliant, full stop.
HTTPS-only assets: mixed content gets your description hidden
Every external resource your template references — images, stylesheets, fonts — must load over https://. An http:// image URL inside an otherwise fine description makes the listing non-secure.
The consequence isn't hypothetical: eBay flags listings with non-secure content, and instead of rendering your full description it can show a warning and make buyers click through to see it. Most buyers don't click through. Modern browsers pile on by blocking mixed content on their own.
This is one of the most common failures in old templates, because a decade ago http:// image hosting was normal. The fix is mechanical: search your description HTML for http:// and replace or rehost every asset it finds. Note that the host must actually serve HTTPS — rewriting the URL to https:// only works if the server supports it.
Mobile rendering: where most old templates lose sales
The majority of eBay browsing happens on phones, and on mobile eBay may show buyers a simplified or truncated description rather than your full HTML. Templates designed for 1024-pixel desktop screens fail here in predictable ways:
- Fixed-width layouts (tables or divs hard-coded to 900+ pixels) force horizontal scrolling or shrink to unreadable size.
- Multi-column designs cram three columns into a phone screen instead of stacking.
- Tiny fonts and dense text walls that were marginal on desktop become unreadable.
- Huge images blow out the layout and slow the page down.
A mobile-safe template in 2026 uses fluid widths (percentages or max-width rather than fixed pixels), a single-column flow, fonts that are legible at phone size, and images that scale to the container. It also front-loads the content that matters — condition notes, what's included, shipping terms — because if eBay truncates, the top of your description is what survives.
Why InkFrog-era templates break or get suppressed in 2026
Old templates from InkFrog's heyday fail on multiple axes at once, which is why "my listings suddenly look wrong" became such a common complaint this month:
- Dead external assets. InkFrog templates loaded stylesheets and images from InkFrog's servers. When the service shut down on June 1, 2026, those references started failing — layouts collapsed and embedded images went blank inside otherwise-live listings.
- Leftover active content. Templates built before the 2017 ban often still carry script tags and widget embeds. eBay doesn't execute them, so the features are dead weight at best and broken markup at worst.
- HTTP asset references. Pre-HTTPS-era templates are full of
http://URLs, triggering the non-secure handling described above. - Desktop-only layout. Fixed 900-pixel table designs predate mobile-first eBay entirely.
If you're carrying templates from that era, patching them one violation at a time is usually more work than rebuilding on a clean, compliant base. If your tool just shut down and took your templates with it, the step-by-step InkFrog migration guide covers the full repair process, not just templates.
How to test your eBay listing template
You can audit a template in about ten minutes per design. Run every template you actively use through this sequence:
- Search the source for active content.
<script,onclick,onload,javascript:,<embed,<object. Any hit fails. - Search for
http://. Every external URL must be HTTPS, and the asset must actually load over HTTPS. - Load every referenced asset directly. Paste each image and stylesheet URL into a browser. A 404 here means buyers see broken icons — this is how you catch dead CDN references (like InkFrog's
i.frg.imURLs) before buyers do. - View a live listing on a real phone. Not the browser's responsive mode — an actual device. Check for horizontal scrolling, unreadable text, and broken stacking.
- Check what eBay shows by default. Open your listing logged out, on mobile, and see how much of the description renders before any "see full description" interaction. Make sure the part that shows carries your key information.
- Re-test after edits. Compliance isn't one-and-done; a single pasted snippet from an old listing can reintroduce a script tag or an HTTP image.
For tooling support: Sellersperch's template designer runs a mobile-friendly lint on every template and flags eBay policy violations before you publish, and its templates use variable substitution so item titles, specifics, and images flow in automatically — one compliant template can serve thousands of listings. The full toolset is on the eBay listing software page.
A 2026 compliance checklist for eBay listing templates
The short version to keep next to your editor:
- No JavaScript, Flash, plug-ins, or form actions — HTML and CSS only
- Every asset (images, stylesheets, fonts) served over HTTPS
- All assets hosted somewhere you trust to stay up — not a third-party tool's CDN that can vanish
- Fluid, single-column-friendly layout; no fixed pixel widths
- Readable font sizes on a phone screen
- Key selling information (condition, contents, shipping terms) at the top
- Images sized and compressed for mobile load times
- Source is clean HTML — no leftover widget embeds or dead markup from old tools
Frequently asked questions
Can I still use HTML in eBay listing descriptions?
Yes. HTML and CSS are fully allowed and worth using — structured, branded descriptions outperform plain text walls. The ban is specifically on active content: JavaScript, Flash, plug-ins, and form actions.
Are iframes and embedded videos allowed in eBay listings?
Treat script-driven embeds as banned — standard video embed codes rely on JavaScript or plug-ins, which fall under the active content policy. If a snippet you're pasting includes a <script> tag, it doesn't belong in an eBay description in 2026.
Will eBay remove my listing over a non-compliant template?
The common consequences are quieter than removal: active content gets blocked or stripped, non-secure (HTTP) content gets the description hidden behind a warning, and broken mobile rendering costs you conversions without any notice at all. Quiet suppression is arguably worse than removal — nothing tells you it's happening.
My templates came from InkFrog and stopped rendering. What now?
InkFrog shut down on June 1, 2026, taking its hosted assets with it — that's why the layouts collapsed. You need the description HTML cleaned of dead references and your embedded images rehosted. Sellersperch does both automatically during its free InkFrog migration: it imports your HTML, strips references that depended on the old service, substitutes working image URLs, and leaves you with eBay-compliant, mobile-safe descriptions.
Do I need to buy templates, or can I build my own?
Either works if the result passes the checklist above. Building your own is fine for one cohesive design; the advantage of a maintained gallery is that compliance and mobile rendering are someone else's job to keep current. Sellersperch includes a starter gallery on every plan, with a larger designer template pack available as an add-on — see pricing.