iOS Bundle ID Finder and App Store ID Lookup

Bundle IDs and App Store IDs for 17 popular iOS apps

These are the values Apple itself returns for each listing. Every row was read back from itunes.apple.com/lookup?id=… against the United States storefront on 8 August 2026, not copied from another list. Names, prices and screenshots change constantly; the two identifiers below do not, because Apple fixes both when the app record is created.

For anything not listed, use the search box above, or open a listing straight from its number — load Instagram's full App Store record and swap the ID for the app you are after.

Popular apps, one page each

Each page below carries the same two identifiers plus the developer, genre, current version, minimum iOS and last store update Apple returned, with the date it was checked.

• Instagram bundle IDcom.burbn.instagram
• TikTok bundle IDcom.zhiliaoapp.musically
• WhatsApp Messenger bundle IDnet.whatsapp.WhatsApp
• Spotify bundle IDcom.spotify.client
• YouTube bundle IDcom.google.ios.youtube
• Netflix bundle IDcom.netflix.Netflix
• Facebook bundle IDcom.facebook.Facebook
• Snapchat bundle IDcom.toyopagroup.picaboo
• Uber bundle IDcom.ubercab.UberClient
• Gmail bundle IDcom.google.Gmail
• Telegram Messenger bundle IDph.telegra.Telegraph
• Signal bundle IDorg.whispersystems.signal
• Slack bundle IDcom.tinyspeck.chatlyio
• Zoom Workplace bundle IDus.zoom.videomeetings
• X (formerly Twitter) bundle IDcom.atebits.Tweetie2
• Reddit bundle IDcom.reddit.Reddit
• Discord bundle IDcom.hammerandchisel.discord

Bundle ID, App Store ID and App ID are three different things

Most of the time someone says “app ID” they mean one of three identifiers, and picking the wrong one is why a push certificate or an associated-domains entitlement refuses to validate. They are not interchangeable.

App Store Connect adds one more piece of vocabulary: on an app's App Information page the track ID is labelled the Apple ID. It is the same number as the one in the store URL, and it has nothing to do with the Apple ID you sign in with. Apple's App Store Connect API and most third-party analytics tools key on that number, while anything that touches the binary (signing, entitlements, MDM inventory, crash reports) keys on the bundle ID.

Where to find your own app's bundle ID

Four places hold the answer, and they can disagree. That disagreement is itself the diagnosis when a build refuses to install.

1. Xcode. Select the target, then the General tab: the field is Bundle Identifier. It is backed by the PRODUCT_BUNDLE_IDENTIFIER build setting, so if the field looks unexpectedly empty or greyed out, the value is coming from an .xcconfig file and you should search the build settings instead.
2. Info.plist. The key is CFBundleIdentifier. In any project made this decade its value is literally $(PRODUCT_BUNDLE_IDENTIFIER), a reference rather than a string. That is why reading the plist alone often tells you nothing.
3. The built .ipa. This is the one that matters, because it is what actually shipped. An .ipa is a zip; the resolved value sits in Payload/YourApp.app/Info.plist. Drop the file into the IPA inspector to read it, along with the version, minimum OS and embedded provisioning profile, without unzipping anything.
4. The provisioning profile. Its entitlements carry an application-identifier — your Team ID followed by the bundle ID, or a wildcard. The provisioning profile decoder prints it, which is the fastest way to confirm that a profile really covers the app you are signing.

For an Android build the equivalent is the application ID; the APK inspector reads it out of the decoded manifest.

How to find the bundle ID of an app you did not build

You cannot read a competitor's Info.plist, but you do not need to. Apple publishes the mapping. An App Store URL carries the track ID in its last path segment (apps.apple.com/us/app/instagram/id389801252), and Apple's public lookup endpoint turns that number into the rest of the record, bundle ID included:

https://itunes.apple.com/lookup?id=389801252

The response is JSON; the field you want is bundleId. It also works in the other direction, which is the part most people miss: querying ?bundleId=com.burbn.instagram returns the listing. That is how you turn an unfamiliar identifier from an MDM inventory, a crash report or a mobile-config profile back into an app name. Add a country parameter to switch storefront; an app that is not sold in one region returns nothing there while resolving normally elsewhere, and the identifiers are identical either way.

Apple documents a rate limit of roughly twenty calls a minute on this API, so a script that walks a list of apps needs to pace itself. For one-off checks the lookup form at the top of this page is quicker, and it renders the ratings, release notes, screenshots and raw JSON alongside the identifiers.

If you would rather follow the whole process as a walkthrough — how to tell two near-identical search results apart, and what a storefront mismatch looks like when it happens — the longer write-up covers both paths step by step.

Why bundle IDs so rarely match the app's name

Look down the table above and most of the surprises have the same cause. A bundle ID is chosen once, before the first upload, and Apple will not let you change it afterwards. It therefore fossilises whatever the product was called at the moment somebody first hit Archive — through every rename, pivot and acquisition that followed.

• com.burbn.instagram: Instagram was pivoted out of Burbn, a check-in app, in 2010.
• com.toyopagroup.picaboo: Snapchat launched as Picaboo, under a company called Toyopa Group.
• com.atebits.Tweetie2: X was Twitter, and Twitter's iOS app was Tweetie, bought from a developer called atebits.
• com.tinyspeck.chatlyio: Slack was built inside Tiny Speck, the studio behind the game Glitch.
• com.hammerandchisel.discord: Discord's company was named Hammer & Chisel.
• com.zhiliaoapp.musically: TikTok inherited the App Store record of Musical.ly after the 2018 merger.

The practical lesson is narrow but useful: never infer a bundle ID from a company's current name, and never assume the one you were told is right. Look it up. The cost of guessing is a push certificate issued against an identifier no build uses, or a deep link that silently never matches.

What the bundle ID does during beta distribution

iOS keys installed apps by bundle identifier. Two builds sharing one identifier are, as far as the device is concerned, the same app: install the beta and it lands on top of the copy already there rather than beside it. Teams that want a tester to hold both at once give the beta its own identifier (a .beta or .dev suffix is the usual convention), and that identifier has to exist in the developer portal and in the provisioning profile as well, not just in the Xcode target.

Over-the-air installs make this visible. When you upload a build, BetaDrop reads the bundle identifier out of the .ipa and writes it into the itms-services manifest that Safari hands to iOS. iOS compares the identifier in that manifest with the one inside the binary it downloads, so a build whose target, provisioning profile and App ID disagree tends to fail with nothing more useful than an “Unable to install” alert. When that happens, the file is rarely the problem; the identifiers are. The same applies on the Android side when you upload an APK, where the application ID plays the same role.

If an install is failing, check three things in order: the bundle ID in the built binary, the identifier the profile authorises, and whether the tester's device is in that profile at all. The UDID checker answers the third in a couple of taps on the tester's phone.

Frequently asked questions