Convert Instagram media IDs to post creation dates
⚠️ Note: Instagram's public URLs use shortcodes (e.g., /p/ABC123/), not Snowflake IDs. Media IDs are internal identifiers used by Instagram's API and backend systems.
Use Instagram's Graph API or Basic Display API to retrieve media IDs from posts, stories, and reels. The id field contains the Snowflake ID.
Inspect network requests when loading Instagram posts to find media IDs in API responses. Look for GraphQL or REST API calls.
Some Instagram analytics tools expose media IDs for posts. Check your analytics dashboard or API documentation.
Instagram uses Unix epoch (January 1, 1970, 00:00:00 UTC) as its Snowflake epoch (0 milliseconds). This differs from Twitter and Discord which use custom epochs.
💡 Why Unix epoch? Instagram uses the standard Unix epoch with custom sharding logic, making their Snowflake IDs compatible with standard Unix timestamp tools.
Find when photos and videos were uploaded to Instagram. Track content creation timestamps.
Determine post creation timestamps. Useful for content scheduling analysis and engagement tracking.
See when stories were published. Track story posting patterns and timing strategies.
Find reel upload dates. Analyze reel performance based on posting times.
Analyze Instagram post timing and scheduling patterns. Optimize posting times based on historical data.
Verify content upload dates for copyright claims and intellectual property disputes.
Track Instagram activity timelines. Monitor content creation patterns over time.
Debug Instagram API integrations by verifying media ID timestamps and creation dates.
Research Instagram content chronology. Track when viral content was originally posted.
Build Instagram bots and automation tools with accurate timestamp tracking.
Instagram: Uses Unix epoch (0) - January 1, 1970, 00:00:00 UTC
Twitter: Uses custom epoch (1288834974657) - November 4, 2010
Discord: Uses custom epoch (1420070400000) - January 1, 2015
Unlike Twitter and Discord which use custom epochs, Instagram uses the standard Unix epoch. This means Instagram Snowflake IDs represent time since January 1, 1970, making them compatible with standard Unix timestamp tools.
// JavaScript
function decodeInstagramId(id) {
const INSTAGRAM_EPOCH = 0n; // Unix epoch
const snowflake = BigInt(id);
const timestamp = Number((snowflake >> 22n) + INSTAGRAM_EPOCH);
return new Date(timestamp);
}
// Example usage
const date = decodeInstagramId('2345678901234567890');
console.log(date.toISOString());# Python
from datetime import datetime
def decode_instagram_id(snowflake_id):
INSTAGRAM_EPOCH = 0
timestamp = ((int(snowflake_id) >> 22) + INSTAGRAM_EPOCH) / 1000
return datetime.fromtimestamp(timestamp)
# Example usage
date = decode_instagram_id('2345678901234567890')
print(date.isoformat())Instagram handles billions of media uploads across global data centers. Snowflake IDs provide:
Q: Can I get media IDs from Instagram URLs?
A: Instagram public URLs use shortcodes, not Snowflake IDs. You need to use Instagram API or browser DevTools to extract media IDs.
Q: Why does Instagram use Unix epoch?
A: Instagram uses Unix epoch (0) with custom sharding logic, making their IDs compatible with standard timestamp tools while maintaining distributed generation.
Q: Can I decode Instagram story IDs?
A: Yes! Instagram stories use Snowflake IDs. If you have the story ID from the API, you can decode it to see when it was published.
Q: Is this tool free?
A: Yes, completely free with no signup required. All processing happens in your browser for privacy.
Get $200 free DigitalOcean credit or sponsor us on GitHub!