Randomly

Phone token generator

Fake FCM, Apple Push, BlackBerry PIN, and generic device tokens with realistic lengths, for tests and fixtures.

Output · 0 tokens

32 chars

Adjust options to generate tokens.

Format-realistic test placeholders generated locally with cryptographically strong randomness. They are not registered device credentials and cannot receive push notifications.

Seed ·
Formats
4
Generated
locally

Related tools

Phone generator

Sample phone numbers.

UUID generator

RFC 9562 UUIDs.

Password

Strong random passwords.

This phone token generator makes placeholder device tokens for test data. Choose FCM, Apple (APNs), BlackBerry PIN, or Generic, set how many you want, and copy them. Tokens are built in your browser with crypto.getRandomValues. They look right and do nothing, because no push service ever issued them.

How to generate phone or device tokens

  1. Pick a token type: Generic, FCM, Apple, or BlackBerry.
  2. For Generic, set the Length slider anywhere from 16 to 64 characters.
  3. Set How many, from 1 to 20.
  4. Click Generate, then tap a token to copy it or use Copy all.

What each format looks like

FCM is the prefix APA91 followed by 178 URL-safe characters, 183 in total. Apple is 64 lowercase hex characters, the classic 32-byte APNs token written out. BlackBerry is an 8-character hex PIN. Generic is a Base62 string at whatever length you picked. Real push credentials only come from Firebase, Apple, or BlackBerry, so none of these will deliver anything.

Typical uses

  • Checking how a UI handles a 183-character token: wrapping, truncation, copy buttons.
  • Filling token columns in fixture files and test databases.
  • Testing input validation for token length and character set.
  • Generic placeholder IDs or key-shaped strings in a dev environment.

Frequently asked questions

Are these working push-notification tokens?

No. They're placeholders for layouts, validation, fixtures, and databases. Only Firebase, Apple, or BlackBerry can issue a token that is actually registered to a device.

Why is the Apple token 64 hexadecimal characters?

That's the familiar hex form of a 32-byte APNs token, and it's what many test fixtures use. Don't hard-code that length in production code, though. Apple treats device tokens as variable-length binary data.

How random are the generated tokens?

Each character is picked with your browser's crypto.getRandomValues, so the output is unpredictable. That matters less than it sounds here, since the tokens aren't credentials anyway.

What is Base62?

Digits 0 to 9 plus uppercase and lowercase letters, 62 symbols in all. With no punctuation, the strings survive URLs, filenames, and copy-paste without escaping.

Built and maintained by Bipul Kumar. Found a wrong number or a broken result? Tell me and I'll fix it.