How to Find an Instagram User ID for a Comment Picker (Free Finder)

September 21, 2026

Every Instagram account has two identities. The @handle everyone sees, and a numeric ID underneath it that never changes, even when the handle does. For most people that number is trivia. For anyone running giveaways, moderating entries, or connecting a picker to Meta's official API, it's the detail that keeps your records accurate after someone renames their account.

Here's what the ID actually is, why a comment picker cares about it, and three ways to find one.

What an Instagram User ID Actually Is

Instagram assigns every account a permanent numeric identifier the moment it's created, often called the user ID, the numeric ID, or internally the "pk." It's separate from the username, and it's what Instagram's own systems use to reference an account behind the scenes, since usernames are just a label that can be changed at any time.

A few properties worth knowing:

It never changes. Someone can rename their account five times and the numeric ID stays identical throughout.

It's public information. For any public account, the ID isn't a secret. It's embedded in the page data Instagram sends to any browser that loads the profile, and it's returned by Meta's own API for any public request.

Private accounts still have one. The ID exists regardless of privacy settings, though what you can retrieve alongside it differs: a private account's numeric ID is often visible even when its posts and follower list are not.

It's what APIs actually use. Any tool built on Meta's Graph API references accounts by numeric ID internally, even if the interface shows you a username.

Why a Comment Picker Needs This

A username is a moving target. A numeric ID is not, and that difference matters in a few specific giveaway situations.

Permanent exclusions. If you want to permanently exclude your own account, a brand partner's account, or a known repeat entrant from every future draw, filtering by username breaks the moment they change it. Filtering by numeric ID doesn't.

Matching an entrant to a winner after a rename. Someone enters your giveaway as @summer_jane, wins, and by the time you go to verify them they've renamed to @janedoes. If you only recorded the username at entry time, that looks like two different people. The numeric ID resolves it, since it stayed constant through the rename.

Connecting a picker to Meta's official API. If you're using an API-connected tool rather than a URL-based one, working with your own Business or Creator account requires the numeric Instagram Business Account ID at setup, not just the handle.

Building a durable exclusion list. Brands that run giveaways monthly often keep a standing list of accounts to exclude, whether for past policy violations or because they're internal staff. A list built on usernames needs constant upkeep. A list built on numeric IDs doesn't.

Verifying you're looking at the right account. Impersonation accounts copying a real handle with a slightly altered spelling are common on any giveaway with real reach. The numeric ID is one more way to confirm you're crediting or contacting the actual account that entered, not a lookalike.

Method 1: A Free ID Finder Tool

The fastest route for a single lookup. Paste a public username or profile URL into a finder tool, and it returns the numeric ID along with basic public profile details.

Insta Picker includes a free User ID finder built for exactly this: paste a handle, a profile URL, or an @mention, and get the numeric ID back instantly, with no login required for public accounts. It works in reverse too, so if you've got a numeric ID from an old export or an API response and need to know which account it belongs to today, you can look it up either direction.

This is the right method for almost every giveaway use case: checking a handful of accounts for an exclusion list, confirming a winner's identity survived a rename, or spot-checking a suspicious lookalike account.

Method 2: Meta's Official Graph API

The route that actually matters if you're connecting a comment picker to your own Business or Creator account for automated, API-based access.

Broadly, the process runs through Meta's Graph API Explorer:

  1. Confirm your Instagram account is set up as a Business or Creator account and connected to a Facebook Page.
  2. In Graph API Explorer, request your connected Pages to get the numeric Page ID.
  3. Query that Page for its instagram_business_account field. The response includes the numeric Instagram account ID tied to it.

That ID is what an API-connected picker needs during setup to pull comments programmatically from your own posts, and it's also visible in some Meta Business Suite screens, sometimes appearing in the browser's address bar as an asset_id parameter when you're viewing account settings.

This method only works for accounts you manage. It's not a way to look up someone else's ID, since retrieving another account's numeric ID this way requires permissions you won't have unless you administer that account.

Method 3: Checking the Page Source Manually

The technical, no-tool route, useful mainly as a fallback or for a quick manual confirmation.

Public Instagram profile pages include the account's data, including its numeric ID, somewhere in the page's underlying code. In most browsers, opening developer tools, filtering network requests for GraphQL calls made while the profile loads, and inspecting the response for an id field will surface it.

Worth knowing before you rely on this: Instagram changes its front-end code often, so the exact steps and field names shift over time, and this method can simply stop working without warning. It also generally requires being logged into Instagram in that browser session, which is a materially different situation from a URL-based, no-login lookup. Treat this as a last resort, not a primary method.

Using the ID in Your Giveaway Workflow

Once you have the numeric ID for an account you need to track, a few practical ways to use it:

In your exclusion list. Keep host, partner, and known problem accounts on a list by numeric ID rather than username, and update your picker's exclusion filter from that list rather than re-typing handles that might have changed.

In your entry export. If you're saving a spreadsheet of eligible entries as your giveaway record, add a column for numeric ID alongside username wherever you can retrieve it. It future-proofs the record against renames between the draw and any later dispute. The methods for building that export are covered in our guide to exporting Instagram comments to Excel or CSV.

Alongside your deduplication filter. Usernames are what most duplicate-detection runs on, and that's fine for a single giveaway. But if you're cross-referencing entrants across multiple giveaways to catch repeat entries under renamed accounts, the numeric ID is the more reliable key. The broader logic of duplicate handling is in our guide to removing duplicate entries from a giveaway.

In your official rules. If your giveaway rules name specific excluded parties, such as agency staff or a co-host, listing the numeric ID alongside the handle in your internal documentation (not necessarily the public caption) keeps the exclusion enforceable even if that person's account gets renamed mid-promotion. The broader rules structure is covered in our guide to Instagram giveaway rules for 2026.

A Note on Appropriate Use

Every method here works from public information: an account's own numeric identifier, visible to anyone who loads its public profile. That's different from trying to uncover anything an account owner hasn't made public.

Use ID lookups for what they're actually for in a giveaway context: administering your own promotion, keeping accurate records, and verifying you're crediting the right account. They're not a way to access anything about a private account beyond its public ID, and no method described here does that. If a picker tool ever asks you to log in as a condition of a basic public lookup, or promises data about private accounts beyond their public ID, that's a sign to look elsewhere. For giveaways run entirely on public posts, you don't need to log in for any of this at all, a trade-off covered in more depth in our guide to using a comment picker without login.

Quick Reference

MethodWorks forLogin requiredReliability
Free ID finder toolAny public account, either directionNoHigh
Meta Graph APIYour own connected Business/Creator accountYesHigh, official
Page source inspectionPublic accounts, manual confirmationUsuallyVariable, breaks with site changes

Frequently Asked Questions

Why does an Instagram username not work as a permanent identifier?

Usernames can be changed at any time by the account holder, with no history retained on the public profile. A numeric user ID is assigned once and stays fixed for the life of the account, which is why it's the more reliable reference for exclusion lists, records, and API integrations that need to survive a rename.

Can I find the numeric ID of a private Instagram account?

Often yes, since the numeric ID itself is typically still exposed even when an account is private, though what else you can retrieve alongside it is limited. This isn't a way to see a private account's posts, followers, or other non-public information, only its permanent identifier.

Do I need Meta's Graph API to find a user ID?

Only if you're connecting your own Business or Creator account to an API-based tool. For a single lookup on any public account, a free ID finder that works from a pasted username or profile URL is faster and doesn't require any developer setup.

Why would a giveaway host need someone's numeric ID instead of just their username?

Mainly to keep exclusion lists and entry records accurate over time. If your rules exclude specific accounts, or you're tracking a winner across a claim process, a username that changes mid-giveaway can break a username-based check. The numeric ID doesn't change, so it holds up.

Is looking up someone's Instagram user ID against the platform's rules?

No. The numeric ID is part of the public information any account exposes simply by being public, and Meta's own official API returns it for legitimate developer use. It becomes a concern only if it's used to access information the account holder hasn't made public, which none of the methods here do.