Last updated
Snowflake to Timezone Converter
Convert Snowflake IDs from Twitter, Discord, and Instagram to any timezone worldwide. View timestamps in your local timezone, UTC, or any major timezone with automatic daylight saving time adjustments.
Supported Platforms
- Twitter: Tweet IDs, user IDs, DM IDs (epoch: Nov 4, 2010)
- Discord: User, message, server, channel IDs (epoch: Jan 1, 2015)
- Instagram: Media shortcodes from post URLs
Popular Timezones
Common IANA Timezone Names
Americas:
America/New_York (EST/EDT, UTC-5/-4)
America/Chicago (CST/CDT, UTC-6/-5)
America/Denver (MST/MDT, UTC-7/-6)
America/Los_Angeles (PST/PDT, UTC-8/-7)
America/Sao_Paulo (BRT, UTC-3)
Europe:
Europe/London (GMT/BST, UTC+0/+1)
Europe/Paris (CET/CEST, UTC+1/+2)
Europe/Berlin (CET/CEST, UTC+1/+2)
Europe/Moscow (MSK, UTC+3)
Asia/Pacific:
Asia/Tokyo (JST, UTC+9)
Asia/Shanghai (CST, UTC+8)
Asia/Kolkata (IST, UTC+5:30)
Australia/Sydney (AEST/AEDT, UTC+10/+11)
All conversion happens entirely in your browser with full DST support for all 400+ IANA time zones. Your Snowflake IDs are never transmitted to any server.
How It Works
Snowflake IDs store timestamps in UTC. Our converter:
- Extracts the UTC timestamp from the Snowflake ID
- Applies the platform-specific epoch (Twitter, Discord, or Instagram)
- Converts to your selected timezone with UTC offset
- Automatically handles daylight saving time (DST)
Use Cases
- View tweet times in your local timezone
- Coordinate Discord events across timezones
- Analyze Instagram post timing by region
- Convert timestamps for international teams
- Schedule content based on timezone data
- Debug timezone-related issues
Examples
Example 1: Discord Message in Multiple Timezones
Input: 1085000000000000000
Platform: Discord
UTC timestamp: 2023-03-14 00:00:00 UTC
Timezone conversions:
New York (EST/EDT): 2023-03-13 20:00:00 EST (UTC-4)
London (GMT/BST): 2023-03-14 00:00:00 GMT (UTC+0)
Paris (CET/CEST): 2023-03-14 01:00:00 CET (UTC+1)
Tokyo (JST): 2023-03-14 09:00:00 JST (UTC+9)
Sydney (AEDT): 2023-03-14 11:00:00 AEDT (UTC+11)
Los Angeles (PST/PDT): 2023-03-13 17:00:00 PST (UTC-7)
Example 2: Twitter Tweet Timezone Display
Input: 1529877576591609861
Platform: Twitter
UTC: 2022-05-26 18:00:00.123 UTC
For a user in New York (EDT, UTC-4):
Local time: 2022-05-26 14:00:00 EDT
Display: "May 26, 2022 at 2:00 PM"
For a user in London (BST, UTC+1):
Local time: 2022-05-26 19:00:00 BST
Display: "May 26, 2022 at 7:00 PM"
For a user in Tokyo (JST, UTC+9):
Local time: 2022-05-27 03:00:00 JST
Display: "May 27, 2022 at 3:00 AM"
Note: Different date in Tokyo!
Example 3: Daylight Saving Time Handling
Two tweets — one in winter, one in summer (New York):
Winter tweet: 1500000000000000000
UTC: 2023-01-15 12:00:00 UTC
New York: 2023-01-15 07:00:00 EST (UTC-5)
Note: Eastern Standard Time (no DST)
Summer tweet: 1650000000000000000
UTC: 2023-06-15 12:00:00 UTC
New York: 2023-06-15 08:00:00 EDT (UTC-4)
Note: Eastern Daylight Time (DST active, UTC-4 not UTC-5)
The converter automatically applies the correct
UTC offset based on the date, handling DST transitions.
Frequently Asked Questions
Enter the Snowflake ID, select the platform (Twitter, Discord, or Instagram), and choose your desired timezone. Our converter extracts the timestamp and displays it in your selected timezone, including UTC offset and daylight saving time adjustments.
All major timezones are supported including EST, PST, GMT, CET, JST, AEST, and more. You can convert Snowflake IDs to any timezone worldwide, with automatic daylight saving time handling.
No, Snowflake IDs store timestamps in UTC (Coordinated Universal Time). Our converter takes this UTC timestamp and converts it to your selected timezone for display, accounting for UTC offsets and DST.
Yes! Our converter displays the timestamp in your selected timezone, UTC, and your browser's local timezone simultaneously, making it easy to compare times across different regions.