Xid is a globally unique id generator. Xids are small, fast to generate, sortable, compact URL-safe string with no configuration or central generator server.
Package selection guidance compiled from public package information, community data, and project usage.
Xid is a lightweight, high-performance globally unique ID generator designed for use across multiple platforms. It produces compact, URL-safe strings that are sortable and require no configuration or central server. Ideal for distributed systems, Xid ensures uniqueness without overhead, making it suitable for databases, session tokens, and API identifiers. The package is simple to integrate via Flutter's pub system and supports all major platforms including Android, iOS, Web, macOS, Windows, and Linux.
Use cases
Database primary keys
Session identifiers
API request tracking
Distributed system coordination
URL-safe token generation
Key features
Compact and URL-safe output
No external dependencies
Sortable IDs
Fast generation
Cross-platform support
No configuration required
Suitable for
Backend services
Mobile apps
Web applications
Microservices
High-throughput systems
Considerations
Not cryptographically secure by default
Limited to UUID-like uniqueness guarantees
Best suited for non-sensitive identifiers
Does not provide randomness beyond deterministic generation
Not recommended for cryptographic secrets
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
ReadMe is from that project (with some modifications for dart).
Package xid is a globally unique id generator library, ready to be used safely directly in your server code.
Xid is using Mongo Object ID algorithm to generate globally unique ids with a different serialization (base64) to make it shorter when transported as a string:
https://docs.mongodb.org/manual/reference/object-id/
4-byte value representing the seconds since the Unix epoch,
3-byte machine identifier,
2-byte process id, and
3-byte counter, starting with a random value.
The binary representation of the id is compatible with Mongo 12 bytes Object IDs.
The string representation is using base32 hex (w/o padding) for better space efficiency
when stored in that form (20 bytes). The hex variant of base32 is used to retain the
sortable property of the id.
Xid doesn't use base64 because case sensitivity and the 2 non alphanum chars may be an
issue when transported as a string between various systems. Base36 wasn't retained either
because 1/ it's not standard 2/ the resulting size is not predictable (not bit aligned)
and 3/ it would not remain sortable. To validate a base32 xid, expect a 20 chars long,
all lowercase sequence of a to v letters and 0 to 9 numbers ([0-9a-v]{20}).
UUIDs are 16 bytes (128 bits) and 36 chars as string representation. Twitter Snowflake
ids are 8 bytes (64 bits) but require machine/data-center configuration and/or central
generator servers. xid stands in between with 12 bytes (96 bits) and a more compact
URL-safe string representation (20 chars). No configuration or central generator server
is required so it can be used directly in server's code.