Download websites that use Supersized

About Supersized

There was a stretch of years when the front page of a creative business was a full-screen photograph that dissolved into another full-screen photograph. Supersized is one of the tools that made that possible, a jQuery plugin that stretched images to fill the viewport at any resolution, cycled them on a timer and offered a few transitions on the way. The look dated quickly. The code did not disappear with it.

Released in 2009 under MIT and written in JavaScript, the plugin came out of an agency side project rather than a company, and there is no vendor behind it in the dataset. As of September 2026 we still find it on 33,738 sites in the JavaScript graphics category, 8,261 of them in United States, mostly on .com domains.

Version numbers here measure something other than maintenance. 29 versions appear across the population and 3.2.7 is the one we see most often, but the project stopped moving long ago, so the version a site carries is closer to a build date than to an upgrade record. Whichever copy the freelancer downloaded is the copy that is still being served.

What the plugin implies about a site is therefore specific. There is jQuery on the page, almost certainly an old release of it. The design fashion places the build in a fairly narrow window. The site is likely a portfolio, an agency page, a restaurant, a venue or a photographer, built once by a contractor and handed over, and the asset is served from the site's own directory rather than from a package the host could update. Nobody has audited the front end since, because auditing it would have removed the plugin.

That makes the population useful in two different trades. Redesign and hosting businesses treat it as a list of sites whose owners are still paying for something built a long time ago. Security and asset inventory work treats it as an example of the long tail of unmaintained third-party code that keeps executing in visitors' browsers years after the project behind it went quiet, which is a cleaner illustration of that problem than most abandoned dependencies because the file is visible in the page source.

The honest limit is that detection depends on recognising the script by its file name and path. A site that concatenates it into one minified bundle, renames it or copies fragments of it into a theme will not be counted, and older sites are also the ones most likely to vanish from crawls entirely when they go offline between releases. The count is a floor for a technique that was more widely used than any single plugin.

A per-domain check tells you whether one site still loads the plugin. The download tells you how large the surviving cohort is, where it is registered, and how much of it disappears from one release to the next, which is the only way to see the rate at which a decade-old build era is actually being retired.