free tool

Is the Meta Pixel installed on this site?

Paste any URL. We read the page source and tell you whether the Meta Pixel (formerly the Facebook Pixel) is there, plus the pixel ID if we find one.

Free, no signup. We read only public page content.

free tool

How to know if a website uses the Meta Pixel (Facebook Pixel)

Open the page's source (Ctrl+U, or Cmd+Option+U on a Mac) and search for fbq, fbevents.js, or facebook.com/tr. If the Meta Pixel is installed you'll find a numeric ID passed to fbq('init', '…'). Don't want to dig through code? Paste the URL above.

1

Read the page source

Right-click the page, choose “View page source” or press Ctrl+U, and search for fbq. A match means the pixel is on that page.

2

Check the Network tab

Open DevTools (F12), go to Network, filter for fbevents, then reload. A request to connect.facebook.net confirms the pixel is loading, even when it's added through a tag manager.

3

Use the Meta Pixel Helper

Meta's own Pixel Helper Chrome extension shows every pixel on a page, the IDs, and the events firing. Useful when you want to see what's being tracked, not just whether a pixel exists.

4

Paste it above

The fastest option when you just want a yes or no and the pixel ID. No extension, no DevTools, works on any URL.

questions

the Meta Pixel, answered.

Yes. Facebook renamed the Facebook Pixel to the Meta Pixel in 2022. The code is the same fbq() snippet that loads fbevents.js, so older guides calling it the Facebook Pixel still apply.
It's a 15 to 16 digit number passed to fbq('init', '...'), like fbq('init', '1234567890123456'). One site can run more than one pixel, so finding several IDs is normal.
The pixel runs in the browser and sends events from the visitor's device. The Conversions API (CAPI) sends events from the advertiser's server. Many sites run both. If a site uses CAPI only, the browser pixel may not appear in the page source even though Meta is still receiving events.
It might load through Google Tag Manager or a consent platform, or fire only after a visitor accepts cookies, so it isn't in the raw HTML we read. The Network tab catches those cases: filter for fbevents and reload.
Yes. The snippet sits in public page source, so anyone can see whether a pixel is present and its ID. You can't see their audiences, events, or conversion data, only that the pixel is there.
The check is free and reads only public page source. We don't save the URLs you enter.