Multi-host support
Recognises facebook.com, m.facebook.com, mbasic.facebook.com, business.facebook.com, fb.com, and fb.me. URLs from any of these hosts route through the same parsing logic.
Find Facebook ID extracts the numeric ID from any Facebook URL — profile, page, group, post, photo, video, or event — by parsing the URL directly in your browser. For vanity usernames where the ID is not visible in the URL, the tool surfaces the manual steps to retrieve the ID from page source.
Find Facebook ID is a free, browser-based tool that takes a Facebook URL and returns the underlying numeric ID. Facebook uses these IDs across the Graph API, the Marketing API, and many automation workflows; surfacing them from a human-friendly URL is a small but constant task for advertisers, developers, and community managers.
Find Facebook ID handles every common URL shape: profile.php with an id query parameter, /groups/<id> for groups that use numeric URLs, /pages/Name-<id> for legacy pages, /photo/<id>, /events/<id>, /watch?v=<id>, and post URLs like /<user>/posts/<id>. For each, it parses the structure of the URL and surfaces the ID directly. Vanity usernames (like /zuck or /<your-page-name>) do not include the numeric ID in the URL — for those, the tool explains how to retrieve the ID from page source while logged into Facebook.
Typical users are Facebook Marketing API developers preparing campaigns by audience ID, community managers building tooling that references their groups by numeric handle, content reviewers cataloguing public posts, and analysts joining Facebook data with internal CRM records. Because Find Facebook ID parses the URL locally in your browser, the URLs you look up — including internal team pages or unannounced campaign assets — are never uploaded.
Recognises facebook.com, m.facebook.com, mbasic.facebook.com, business.facebook.com, fb.com, and fb.me. URLs from any of these hosts route through the same parsing logic.
The tool labels the URL as profile, page, group, post, photo, video, event, or vanity username, so you know what kind of identifier you are working with.
For vanity usernames, the tool explains the View Page Source lookup that retrieves the numeric ID — useful when Facebook does not expose it in the URL itself.
Recognises profile.php?id=…, photo.php?fbid=…, watch?v=…, and story_fbid=… query parameters in addition to path-based IDs.
A Copy button moves the ID to your clipboard so you can paste it directly into your Graph API client, ad manager, or spreadsheet.
All work happens in your browser. Internal team URLs, private business pages, and unannounced campaign assets stay confidential during lookup.
Every Facebook object has a numeric ID assigned by the platform. Profiles, pages, groups, posts, photos, videos, and events all share this property — internally, Facebook refers to them by number, and externally, those numbers appear in the Graph API, the Marketing API, the Business Manager, and many third-party tools. The friendly URLs that humans see — /zuck, /facebook, /groups/<name> — are aliases that resolve back to a numeric ID.
When the friendly URL itself contains the number, parsing it is straightforward: split the path, pick the segment, and validate that it consists of digits. Find Facebook ID handles the common cases (profile.php?id=…, /groups/<id>, /pages/Name-<id>, /photo/<id>, /events/<id>, /watch?v=<id>, /<user>/posts/<id>) automatically.
When the URL uses a vanity username instead, the numeric ID is not visible in the URL. Facebook does not expose a public CORS-safe endpoint that returns the ID for a username, which means the tool cannot fetch it directly from the browser. The fallback is to open the URL while logged into Facebook and search the page source for "userID", "page_id", or "group_id" — that value is the numeric ID.
Input
https://www.facebook.com/profile.php?id=100012345678Output
100012345678When passing a Facebook reference to a teammate or vendor, the numeric URL (e.g. /profile.php?id=…) is more durable than a vanity URL because vanity usernames can change. Capture the ID with this tool and store it alongside the friendly URL.
A page ID and a profile ID are different namespaces in the Graph API. Always confirm what kind of object you are looking at — Find Facebook ID labels the result for you, so use that label when constructing API calls.
When the tool reports a vanity username, follow the View Source steps it provides. The numeric ID is consistent across Facebook surfaces and remains valid even if the username changes later.
Once you have an ID, store it in your CRM, project notes, or campaign tracker. Repeat lookups waste time and produce identical results.
Facebook restricts certain uses of public data. Stick to URLs you have legitimate reason to inspect, and avoid bulk scraping that could trigger automated abuse detection.
Make sure the URL starts with facebook.com, m.facebook.com, business.facebook.com, fb.com, or fb.me.
That is expected — Facebook does not expose the ID for vanity URLs. Follow the View Source steps the tool shows.
When the URL is /zuck or /facebook, the numeric ID is not in the URL. The tool explains the View Source fallback so you can retrieve it manually with one extra step.
Facebook surfaces objects through many URL formats. The tool handles each common variant (profile.php, /groups/, /photo/, /watch, story_fbid) so you do not have to remember which extractor to use.
m.facebook.com and mbasic.facebook.com sometimes produce slightly different URL shapes than www.facebook.com. The tool normalises all of them.
A page ID is not interchangeable with a profile ID or a group ID. The tool labels what it found so you do not accidentally pass the wrong ID to a Graph API call.
The tool produces a clean numeric ID with a one-click copy button, which is easier to send over chat than asking a colleague to inspect View Source themselves.
No. The tool parses the URL you paste directly in your browser. No API key is required and no request is sent to Facebook, which is why vanity usernames need a manual fallback — Facebook does not expose a CORS-safe endpoint that maps username to numeric ID.
It finds the ID whenever the URL contains it (profile.php?id=…, /groups/<id>, /pages/Name-<id>, /photo/<id>, /events/<id>, /watch?v=<id>, /<user>/posts/<id>). For vanity usernames it provides the manual View Source steps Facebook itself documents.
Yes. All parsing runs in your browser. The URL is never uploaded to a server, which makes the tool safe to use with internal pages, unannounced campaigns, or any other URL that should not leak.
Vanity URLs like /zuck do not contain the numeric ID. Facebook used to expose the ID through a few public endpoints, but most are now restricted by CORS and authentication. The fallback is to open the URL while logged into Facebook and search the page source for "userID".
Yes. business.facebook.com, web.facebook.com, and standard www.facebook.com share the same URL structures. The tool recognises all of them.
Yes. Once you have the numeric ID, pass it to the Graph API endpoint appropriate to the object type — /v18.0/{user-id}, /v18.0/{page-id}, or similar. Marketing API audience targeting also accepts numeric IDs directly.
Public IDs are public information by design. Use this tool only for purposes consistent with Facebook's terms — building API integrations, validating your own accounts, joining your own CRM data. Avoid bulk scraping or any use that targets users without consent.
No, only Facebook. Instagram and Threads use different URL structures and ID schemes. For those platforms, use the official Meta documentation for the relevant API.
Find Facebook ID turns any Facebook URL into a numeric ID in one click, privately in your browser — saving developers, marketers, and community managers the constant URL-to-ID translation step.