Find the numeric ID in a public profile's HTML.
No paid API. No sign-in here. No guessed numbers.
The extractor looks for supported profile metadata and structured account data. It matches the username or profile URL before displaying an ID. Pasted HTML can be changed or outdated, so extraction is not independent identity verification.
The platform may return a login wall, bot check, redirect or HTML without the ID. Source formats also change. Automatic access stops on a block; no passwords, session cookies or bypass techniques are used. An unsuccessful extraction does not prove that an account is missing.
No. This version has no paid data-service dependency and no API key. The website never asks you to sign in to a social network. Reading pasted source works locally; requesting a public page requires the deployed PHP endpoint.
No. The public page must be accessible and contain a supported, unambiguous ID for the requested profile. Platforms often limit automated access. Use the local source option when you already have public HTML you are allowed to inspect.
Instagram uses supported username-matched account data or profile metadata. TikTok uses the user ID paired with the matching uniqueId, not a video ID or secUid. Twitter/X uses username-matched user data when the public HTML contains a numeric rest_id, id_str, or user id. Tweet/status IDs and unrelated viewer IDs are not accepted.
Saved source may be old or altered, and HTML structures can change. Conflicting IDs are rejected rather than guessed. Always check the displayed source and profile link. An ID does not establish account ownership or recover an account.
It supports source extraction and supported profile links. Automatic page fetching needs PHP hosting. All ten original image, text and calculation tools remain available.