If you came here to install the Facebook Comments plugin on your site, there is something you need to know first: Meta shut it down. The Comment plugin and the Like button for external websites were both discontinued on 10 February 2026. The code does not error, it simply renders as an invisible element, which is why so many sites still carry a comment box that no longer appears. This guide covers what happened, how to remove the dead markup cleanly, and what to replace it with.
Quick answer: The Facebook Comments social plugin was retired on 10 February 2026 and now renders as a zero by zero pixel element. New integrations are not possible. Remove the fb-comments div and the SDK script, then move to native comments, a hosted service such as Disqus or Commento, or a self hosted option like Isso. Historic comments are not migrated automatically, so export anything you need first.
Meta announced the change on 10 November 2025, giving three months of notice. In the announcement, engineers Thuan Le and Jennifer Lin described the plugins as reflecting an earlier era of web development whose usage had naturally declined. That is a polite way of saying almost nobody used them any more, and the ones who did were mostly older sites nobody had touched in years. The retirement notice still sits at the top of the Comments plugin documentation.
What changed and when
Source: Meta for Developers social plugins documentation and announcement.
Why the silent failure caught people out
A plugin that throws an error gets fixed. A plugin that renders an invisible element does not. Sites kept passing automated checks, the SDK kept loading, nothing appeared in the console, and the comment section simply stopped existing. If your analytics show engagement falling off a cliff in February 2026 on article pages, this is a candidate cause.
Check quickly by opening any page that used the plugin and inspecting for a div with class fb-comments. If it is there with no rendered iframe inside it, you are running dead code.
Removing the dead integration
Take out both halves. The container and the SDK.
<!-- remove the container -->
<div class="fb-comments"
data-href="https://example.com/article"
data-width="100%"
data-numposts="10"></div>
<!-- remove the root and the SDK loader -->
<div id="fb-root"></div>
<script async defer crossorigin="anonymous"
src="https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v21.0"></script>
<!-- and the app id meta tag if nothing else uses it -->
<meta property="fb:app_id" content="000000000000000" />Keep the SDK only if you still use Facebook Login or another Meta feature on the same pages. If comments were the only reason it was there, dropping it removes a third party script, a set of cookies and a measurable amount of load time from every page. Our explainer on Facebook API authentication and access tokens covers what else depends on it.
Tip: On WordPress, most Facebook comment integrations came from a plugin rather than theme code. Deactivate and delete the plugin instead of editing templates, then search the theme for fb-comments to catch anything hard coded into a single page template.
Getting your old comments out
This is the part people leave too late. Comments posted through the plugin lived on Facebook’s side, attached to the URL, and there is no export button waiting for you.
If the threads still render anywhere in your Meta tooling, copy them out manually while you can. If they do not, the practical options are your own page cache, the Internet Archive, or an old database backup if your integration mirrored comments locally. Many did not. Treat anything you cannot retrieve today as gone, and prioritise the handful of pages where the discussion had genuine value.
Warning: Do not leave the empty container in place hoping it comes back. Meta described the retirement as permanent, and an orphaned div plus an unused SDK is a privacy and performance liability with no upside. It also means visitors see an article that appears to have no comment section rather than one inviting them to comment.
What to replace it with
The right answer depends on how much moderation you are willing to do and how you feel about third party scripts.
| Option | Hosting | Best when | Watch out for |
|---|---|---|---|
| Native platform comments | Yours | WordPress, Ghost and similar already have it built in | Spam, so pair it with a filter |
| Disqus | Third party | You want zero infrastructure and a familiar interface | Ads on free tiers, heavy script, tracking |
| Commento or Remark42 | Third party or self hosted | Privacy matters and you can run a container | You own uptime and moderation |
| Isso | Self hosted | Static sites, small audiences, no accounts wanted | Minimal features by design |
| giscus | GitHub Discussions | Developer audience, documentation sites | Commenters need a GitHub account |
| Link to a social post | None | Discussion already happens off site | You lose the content and the SEO value of it |
One thing the Facebook plugin genuinely did well was identity. Real names attached to real profiles kept threads calmer than anonymous boxes usually manage. If that mattered to your community, choose a replacement with social sign in rather than a fully anonymous option, and accept that you are trading some friction for civility.
Note: Not every Meta social plugin is gone. The Comment and Like buttons were retired, but embedded posts, videos and the Page plugin were not part of this announcement. Check the current documentation before assuming any given integration still works, and the same caution applies to the mobile side, which we cover in using the Facebook SDKs in app development.
Rebuilding comments the sensible way
Whatever you choose, three decisions save pain later.
Key comments to a stable identifier. Use the post ID or a permanent slug, not the full URL. The Facebook plugin keyed to data-href, which is exactly why comment threads vanished whenever a site changed domain or moved to HTTPS.
Load comments on demand. Render a button that mounts the comment component on click. Comment widgets are among the heaviest third party scripts on a typical article, and most readers never scroll to them.
Own the data. Pick something that exports to JSON or sits in your own database. The lesson of February 2026 is that a free hosted feature is a dependency, and dependencies get retired. It is the same pattern that ended automatic posting to a user timeline years earlier.
Frequently asked questions
Can I still add Facebook comments to my website?
No. The Comment plugin was discontinued on 10 February 2026 and new integrations are not possible. Any tutorial that tells you to paste an fb-comments div was written before that date and will produce an invisible element.
Why did my Facebook comment box disappear without an error?
Meta chose to degrade the plugin gracefully rather than break pages. It renders as a zero by zero pixel element, so nothing throws and nothing logs. That is deliberate, and it is why the change went unnoticed on many sites for months.
Are my old Facebook comments recoverable?
Usually not in any automated way. The comments lived on Meta’s infrastructure keyed to your page URL, and there is no export path. Check page caches and archives for the pages that matter most, and plan on rebuilding from there.
Does removing the SDK affect Facebook Login?
Yes, if your login flow uses the JavaScript SDK. Remove the comment container first, confirm nothing else on the page calls the SDK, and only then remove the loader. Our guide to Facebook Login covers what the SDK is still needed for.
Is the Like button gone too?
Yes. Both the Like button and the Comment plugin for external websites stopped working on the same date. Share buttons that simply link to Facebook’s sharer URL are unaffected, because they are ordinary links rather than plugins.
The bottom line
The Facebook Comments plugin was a convenient way to bolt a discussion onto a page without running anything yourself, and it is now dead code sitting in thousands of templates. Strip it out, take the performance and privacy win, and replace it with something you can export. If a comment section is worth having at all, it is worth owning.
