AddThis

What Is AddThis?

AddThis was a widely used social sharing and audience-engagement tool that let website owners add share buttons, follow buttons, and related content widgets to their pages with a single embedded snippet. For well over a decade it was one of the most recognizable third-party sharing tools on the web, appearing on a vast number of blogs, news sites, and ecommerce stores as the row of "share to Facebook, Twitter, Pinterest, email" buttons that visitors used to spread content.

The most important fact to state up front is that AddThis has been discontinued. The service was shut down in 2023, and its sharing and follow tools no longer function as a live, supported product. This matters enormously for anyone analyzing websites today: when you detect AddThis on a site, you are almost always looking at a legacy embed, leftover code from when the service was active, rather than a functioning feature. A responsible profile treats AddThis primarily as a historical and detection-relevant technology, not as a tool to recommend or implement now.

During its active life, AddThis was a free service for site owners, monetized in part through the data its widgets collected as they were embedded across millions of sites. It was owned over its history by several companies and ultimately by Oracle, which operated it within its advertising and data business before winding the product down. The widget loaded from AddThis's own content domains and injected sharing interfaces into the page, which is why its fingerprints are still easy to recognize in legacy code.

AddThis was never a browser extension or a platform a visitor installed; it was a third-party JavaScript widget embedded by the website owner. Because it loaded recognizable scripts from addthis.com domains and injected distinctive markup, it is straightforward to detect even now, with the crucial caveat that detection today indicates a remnant of a service that has been retired rather than an active integration.

It is worth dwelling on why a discontinued tool is still worth profiling. The web is full of long-lived pages that were built years ago and never fully maintained, and embedded third-party widgets are among the most common pieces of code left behind when a service shuts down. AddThis is a textbook example: countless sites still carry its snippet in their templates, meaning the script reference and markup persist even though the buttons no longer do anything useful. For technology detection, this makes AddThis a marker of a site's age and maintenance habits as much as of any current capability, which is a genuinely useful signal in its own right.

How AddThis Worked

While it was operational, AddThis followed the standard third-party widget pattern. A site owner created an account, configured which buttons and tools they wanted, and copied a small JavaScript snippet into their site's templates. That snippet loaded the AddThis client script from AddThis's content delivery domains, which then rendered the requested interfaces into the page's DOM.

The core offering was share buttons, a configurable set of icons that let visitors share the current page to social networks, messaging apps, or email. AddThis also provided follow buttons linking to a brand's own social profiles, related-content and recommendation widgets that suggested other pages to keep visitors on the site, and various list-building and audience tools. Site owners could choose inline button rows, floating sidebars, or expanding menus, and could customize styles and the selection of services shown.

A defining aspect of AddThis was the data and personalization layer behind the buttons. Because the same widget was embedded across an enormous number of websites, the service was able to observe activity at scale and build audience data, which underpinned its personalization features and its value to the advertising business that owned it. The widget set cookies and communicated with AddThis's servers as part of this model. This data dimension is part of why, in the privacy-focused regulatory environment that developed in the early 2020s, an always-on third-party tracker embedded site-wide became increasingly scrutinized, context that helps explain the product's eventual wind-down.

Technically, the script ran client-side: it loaded after the page, injected button markup and supporting elements into the DOM, attached click handlers that opened share dialogs or recorded interactions, and exchanged requests with AddThis's infrastructure. Because the integration was entirely owned by the site, removing AddThis required editing the site's templates to delete the snippet, which is precisely why so many sites never removed it and still carry the code today.

With the service discontinued, the practical reality is that these mechanisms no longer operate as intended. The script endpoints are no longer a supported, functioning service, so legacy embeds typically render nothing useful, fail silently, or leave inert markup. From a detection standpoint the embed is still visible in the page's HTML and network behavior, but from a functionality standpoint it is a dead feature. Anyone auditing a site that still references AddThis should treat it as cleanup-worthy leftover code rather than a working tool, and should also consider the performance and privacy implications of loading, or attempting to load, a retired third-party script.

How to Tell if a Website Uses (or Used) AddThis

AddThis leaves clear, recognizable fingerprints, which is why it remains easy to spot even after discontinuation. StackOptic checks these from the server side and in the page markup, and you can verify the same signals manually. Throughout, remember the key framing: finding these signals today indicates legacy code from a discontinued service, not an active integration.

The AddThis script domain. The clearest signal is a script reference to AddThis's content domains, classically addthis.com and its CDN host s7.addthis.com (for example a reference to s7.addthis.com/js/300/addthis_widget.js). A request or reference to an addthis.com host is a direct, unmistakable indicator.

Distinctive class names. AddThis buttons are marked up with characteristic class names prefixed addthis_, such as addthis_toolbox, addthis_button_facebook, addthis_inline_share_toolbox, and similar. Seeing addthis_-prefixed classes in the HTML is a strong tell.

The global configuration object. Implementations often defined an addthis_config and/or addthis_share JavaScript object, or called addthis.init. Spotting these globals in the page source confirms an AddThis embed.

A profile/public ID parameter. The widget script was commonly loaded with a pubid (publisher ID) query parameter identifying the account. A script URL containing pubid=ra- is characteristic of AddThis.

Leftover button markup. Even when the buttons no longer render usefully, the container elements and icon markup frequently remain in the DOM, visible when you inspect the page.

Method	What to do	What AddThis reveals
View Source	"View Page Source" and search for addthis	The addthis_widget.js reference, addthis_ classes, config objects
Browser DevTools	Inspect button elements and the Network tab	addthis_-prefixed DOM classes and any requests to addthis.com hosts
curl -I / curl -s	`curl -s https://example.com	grep -i addthis`
Wappalyzer	Run the extension on the live page	Often identifies "AddThis" under widgets/sharing
BuiltWith	Look up the domain	Current and historical AddThis presence

A quick command-line check is curl -s https://example.com | grep -i "addthis". A match indicates AddThis code is present, which, given the 2023 shutdown, almost certainly means a legacy embed. For broader methodology on spotting embedded tools, see our guides on how to find out what technology a website uses and how to check what javascript libraries a website uses.

There is an important interpretive nuance here that sets AddThis apart from most tools in a detection catalog. For an active service, detecting it tells you about a site's current capabilities. For AddThis, detection tells you about a site's history and maintenance: the presence of addthis_widget.js or addthis_ classes strongly suggests the page was built or last meaningfully updated while AddThis was alive, and that nobody has since pruned the dead snippet. That makes AddThis a useful proxy signal for site age, technical debt, and how actively a site is maintained. Server-side analysis is well suited to surfacing this because it reads the raw HTML and references directly, even when the script itself no longer does anything in the browser.

Key Features

These features describe AddThis as it operated before discontinuation, and are presented for historical and detection context.

• Social share buttons. Configurable icon rows for sharing the current page to social networks, messaging apps, and email.
• Follow buttons. Links to a brand's own social profiles to grow followers.
• Related-content widgets. Recommendation modules suggesting other pages to retain visitors.
• Multiple placements. Inline, floating sidebar, and expanding-menu button layouts with style customization.
• Audience and personalization data. A cross-site data layer that powered targeting features and the underlying advertising business.
• Simple embed. A single JavaScript snippet to deploy all selected tools site-wide.

Pros and Cons

Because AddThis is discontinued, the most relevant "con" is its retired status. The points below describe its historical strengths and the issues that are pertinent today.

Pros (historical)

• Extremely easy to deploy, a single snippet added sharing and follow tools across a site.
• Broad coverage of social networks and sharing destinations in one widget.
• Free for site owners, with flexible placements and styling.
• Familiar, recognizable interface that visitors understood.

Cons (and current concerns)

• The service is discontinued (shut down in 2023), so embeds no longer function as a supported product.
• Legacy embeds leave dead code that adds page weight and clutter without delivering working features.
• As a cross-site third-party tracker, it raised privacy considerations under modern regulations.
• Loading or attempting to load a retired third-party script can hurt performance and should be cleaned up.

AddThis vs Alternatives

With AddThis discontinued, site owners who still rely on it need a replacement, and analysts comparing legacy widgets need context. The table contrasts AddThis with current options.

Tool	Status	Approach	Notes
AddThis	Discontinued (2023)	Third-party share/follow widget	Detection today means legacy code
AddToAny	Active	Third-party sharing buttons/plugin	A common, still-supported alternative
ShareThis	Active	Third-party sharing widget	Another established sharing service
Native share links	Active	Hand-coded share URLs	No third-party script; lightweight and private
Web Share API	Active (browser)	Built-in OS share sheet	Uses the device's native sharing, no widget

For sites cleaning up after AddThis, a frequently chosen modern equivalent is AddToAny, which provides comparable sharing buttons as a supported product. For the broader skill of spotting and cataloging embedded scripts, our guide on how to check what javascript libraries a website uses is directly applicable, and the data-collection angle of widgets like AddThis connects to using tech-stack data to qualify leads.

Use Cases

The honest framing of AddThis use cases is largely retrospective. While it was active, AddThis was used by blogs, news and media sites, ecommerce stores, and marketing pages that wanted to encourage social sharing and grow their following with minimal effort. It was especially common on content-heavy sites where shareability mattered, and its ubiquity made it a default choice for years.

Today, the practical "use case" for knowing about AddThis is detection and remediation. When you find AddThis on a site, the appropriate action is usually to recognize it as leftover code and consider removing it, both to reduce unnecessary page weight from a non-functional script and to eliminate a retired third-party reference. Site owners who valued the sharing functionality should migrate to a supported alternative or to lightweight native share links rather than leaving the dead AddThis snippet in place.

For technology research and competitive analysis, detecting AddThis is a particularly informative signal precisely because the service is gone. Its presence strongly suggests a site that was built or last substantially updated some years ago and has not been thoroughly maintained since, which is valuable context when profiling a prospect's technical sophistication or estimating the scope of a modernization or migration engagement. An agency, for instance, might treat AddThis detection across a list of prospects as a flag for sites likely carrying broader technical debt and overdue for a refresh. Surfacing that signal automatically across many domains, rather than inspecting each site by hand, is exactly the kind of insight a technology-detection scan delivers, and the connection between embedded-widget data and prospect qualification is explored further in our overview of technographics for lead qualification.

Frequently Asked Questions

Is AddThis still available?

No. AddThis was discontinued and shut down in 2023. The sharing and follow tools are no longer a live, supported product, so any AddThis code you find on a website today is almost certainly a legacy embed left over from when the service was active. Site owners still relying on it should migrate to a supported alternative, and anyone auditing a site should treat the AddThis snippet as dead code to clean up.

Why does a website still show AddThis code if the service is gone?

Embedded third-party widgets remain in a site's templates until someone manually removes them. Because many sites are not actively maintained, the AddThis snippet, its script reference and addthis_ markup, often stays in the HTML long after the service was retired. The buttons typically no longer function usefully, but the code persists, which is why detection tools still flag AddThis on older, un-pruned sites.

How can I tell if a site has AddThis embedded?

Search the page source for addthis, look for a script reference to s7.addthis.com/js/300/addthis_widget.js, and look for addthis_-prefixed class names like addthis_toolbox or addthis_inline_share_toolbox. You may also see an addthis_config or addthis_share global object and a pubid=ra- parameter on the script URL. A terminal check like curl -s URL | grep -i addthis will surface these references quickly.

What should I use instead of AddThis?

Because AddThis is discontinued, consider a supported sharing tool such as AddToAny or ShareThis, or, for a lightweight and privacy-friendly approach, hand-coded social share links or the browser's native Web Share API, which uses the device's built-in share sheet without loading a third-party script. The right choice depends on whether you want a managed widget with multiple destinations or the minimal footprint of native links.

Does leftover AddThis code affect site performance or privacy?

It can. A retired third-party script reference still adds to page weight and may trigger failed network requests, which is wasteful even when the feature no longer works. Historically AddThis also acted as a cross-site data collector, so its presence is relevant in privacy reviews. Removing the dead snippet is generally advisable to streamline the page and eliminate an unnecessary, unsupported third-party reference.

Want to detect AddThis and the rest of a site's technology stack instantly? Run any URL through StackOptic at https://stackoptic.com.