Ek Snowflake ID kya hai?

Ek Snowflake Twitter aur Discord dwara use kiya ek 64-bit id hai jo ek millisecond timestamp, ek worker (machine) id, ek process id, aur ek per-millisecond sequence ko ek single sortable number mein pack karta hai, taaki ids ek central counter ke bina unique aur roughly time-ordered hon.

Main ek Discord message ki ID se kaise pata karoon ki woh kab bheja gaya?

Message ya user id ko Decode mein Discord epoch selected ke saath paste karein. Tool 42 timestamp bits shift out karta hai, Discord epoch (1420070400000 ms) add karta hai, aur exact creation time ISO aur Unix milliseconds ke roop mein dikhata hai.

Twitter aur Discord epochs mein kya farak hai?

Dono layouts same bit widths ke hain, lekin woh alag start points se milliseconds count karte hain: Twitter 1288834974657 (Nov 2010) use karta hai aur Discord 1420070400000 (Jan 2015). Galat wale se decode karna har timestamp ko us gap se shift kar deta hai.

Worker aur process 31 par aur sequence 4095 par kyun capped hain?

Layout worker aur process ko 5-5 bits deta hai (2^5 − 1 = 31) aur sequence ko 12 bits (2^12 − 1 = 4095). Un limits se oopar values agle field mein overflow ho jaatin, isliye generator unhe reject karta hai.

Kya main apni khud ki service ke liye ek custom epoch use kar sakta hoon?

Haan. Custom preset chunein aur apna epoch Unix milliseconds mein enter karein. Generate aur Decode phir us value ko use karte hain, jo aapko kisi bhi Snowflake-style scheme ke saath kaam karne deta hai jo 42/5/5/12 bit layout rakhti hai.

Kya jo IDs main generate ya decode karta hoon woh kahin bheje jaate hain?

Nahi. Har bit-shift aapke browser mein BigInt se run hota hai. Jo timestamps, ids, aur field values aap type ya paste karte hain woh kabhi aapke device se bahar nahi jaate aur ArrayKit ko upload nahi hote.

Snowflake ID Generator & Decoder

Twitter ya Discord epochs ke saath 64-bit Snowflake IDs generate aur decode karein, seedhe aapke browser mein. Jo aap enter karte hain woh aapke device se bahar nahi jaata.

Snowflake ID Generator poori tarah aapke browser mein chalta hai. Jo IDs, timestamps, aur field values aap enter ya decode karte hain woh kabhi aapke device se bahar nahi jaate aur kuch bhi ArrayKit ko upload nahi hota.

ULID Generator kholein

Snowflake ID Generator ke baare mein

Snowflake ID Generator 64-bit Snowflake IDs us tarah banata hai jaise Twitter aur Discord karte hain: ek millisecond timestamp, ek worker id, ek process id, aur ek per-millisecond sequence ek BigInt mein packed. Discord ya Twitter epoch preset pick karein, ya apna khud ka epoch Unix milliseconds mein type karein, phir ek ID mint karne ke liye timestamp aur field values set karein. Decode par switch karein taaki koi bhi Snowflake paste karke exact millisecond timestamp, uska ISO time, aur aapke chune hue epoch ke tehat worker, process, aur sequence bits dekhein. Yeh reverse-engineering ke liye handy hai ki ek Discord message kab post hua, ek ID ko ek test fixture mein reproduce karne, ya ek distributed id scheme sanity-check karne ke liye. Saari bit-shifting aapke device par hoti hai; jo IDs aur timestamps aap enter karte hain woh kabhi upload nahi hote.

Features

Ek timestamp, worker, process, aur sequence se ek 64-bit Snowflake generate karein
One-click Discord (1420070400000) aur Twitter (1288834974657) epoch presets
Kisi bhi doosri Snowflake scheme ke liye Unix milliseconds mein custom epoch field
Decode mode kisi bhi Snowflake ko uske timestamp, ISO time, aur field bits mein badalta hai
"Now" button ek current-time ID ke liye aapke clock se timestamp seed karta hai
BigInt math saare 64 bits exact rakhta hai — bade IDs par koi precision loss nahi
Jab worker, process, ya sequence apne bits overflow karein to clear range errors
Poori tarah aapke browser mein chalta hai, koi IDs kisi server ko nahi bheje jaate

Snowflake ID Generator kaise use karein

Discord, Twitter, ya ek custom epoch chunein
Generate mein, timestamp aur worker, process, aur sequence values set karein
Resulting 64-bit Snowflake ID copy karein
Decode par switch karein aur uska timestamp aur fields wapas padhne ke liye ek Snowflake paste karein

Example

Input

175928847299117063  (Discord epoch)

Output

timestamp: 2016-04-30T11:18:25.796Z
worker: 1  process: 0  sequence: 7

Ek Discord Snowflake decode karna recover karta hai ki woh kab bana aur uske field bits.

Common errors aur troubleshooting

Decoded timestamp decades off hai (jaise year 1970 ya 2100). — Aap galat epoch se decode kar rahe hain. Preset ko source se match karne ke liye switch karein — Discord vs Twitter epochs saalon se differ karte hain — ya exact custom epoch set karein.
Generate report karta hai 'Sequence must be between 0 and 4095.' — Sequence field sirf 12 bits ka hai. worker aur process ko 0–31 ke andar aur sequence ko 0–4095 ke andar rakhein taaki har value apne slot mein fit ho.
'Timestamp is before the chosen epoch.' — Ek Snowflake apne epoch se milliseconds store karta hai, isliye timestamp epoch par ya uske baad hona chahiye. Ek later time ya ek smaller epoch pick karein.
Pasted ID rounded lagta hai ya apne last digits kho deta hai. — Snowflakes JavaScript ki safe integer range se aage hote hain, isliye unhe strings ki tarah treat karein. Yeh tool BigInt use karta hai, lekin ek aisa ID paste karne se bachein jise kisi doosre tool ne pehle se ek float ke roop mein parse kar diya.

Aksar pooche jaane wale sawaal

Ek Snowflake ID kya hai?: Ek Snowflake Twitter aur Discord dwara use kiya ek 64-bit id hai jo ek millisecond timestamp, ek worker (machine) id, ek process id, aur ek per-millisecond sequence ko ek single sortable number mein pack karta hai, taaki ids ek central counter ke bina unique aur roughly time-ordered hon.
Main ek Discord message ki ID se kaise pata karoon ki woh kab bheja gaya?: Message ya user id ko Decode mein Discord epoch selected ke saath paste karein. Tool 42 timestamp bits shift out karta hai, Discord epoch (1420070400000 ms) add karta hai, aur exact creation time ISO aur Unix milliseconds ke roop mein dikhata hai.
Twitter aur Discord epochs mein kya farak hai?: Dono layouts same bit widths ke hain, lekin woh alag start points se milliseconds count karte hain: Twitter 1288834974657 (Nov 2010) use karta hai aur Discord 1420070400000 (Jan 2015). Galat wale se decode karna har timestamp ko us gap se shift kar deta hai.
Worker aur process 31 par aur sequence 4095 par kyun capped hain?: Layout worker aur process ko 5-5 bits deta hai (2^5 − 1 = 31) aur sequence ko 12 bits (2^12 − 1 = 4095). Un limits se oopar values agle field mein overflow ho jaatin, isliye generator unhe reject karta hai.
Kya main apni khud ki service ke liye ek custom epoch use kar sakta hoon?: Haan. Custom preset chunein aur apna epoch Unix milliseconds mein enter karein. Generate aur Decode phir us value ko use karte hain, jo aapko kisi bhi Snowflake-style scheme ke saath kaam karne deta hai jo 42/5/5/12 bit layout rakhti hai.
Kya jo IDs main generate ya decode karta hoon woh kahin bheje jaate hain?: Nahi. Har bit-shift aapke browser mein BigInt se run hota hai. Jo timestamps, ids, aur field values aap type ya paste karte hain woh kabhi aapke device se bahar nahi jaate aur ArrayKit ko upload nahi hote.

Related tools

ULID Generator — Sortable ULIDs generate karein, embedded timestamp decode karein, aur ULID aur UUID ke beech convert karein.
UUID Generator — Ek ya kai random UUID v4 values generate karein.
Unix Timestamp Converter — Unix timestamps aur readable dates (local aur UTC) ke beech convert karein.
Hash Generator — Web Crypto API ke through SHA-256 / SHA-1 / SHA-384 / SHA-512.
Number Base Converter — Integers ko binary, octal, decimal aur hexadecimal ke beech convert karein.
Base58 Encoder / Decoder — Bitcoin alphabet se text ya hex ko Base58 encode aur decode karein