Discord tells you when you joined a server. It never tells you when the server itself was created. There is no "founded" date in server settings, nothing on the server profile, nothing in the invite preview. For a platform where a community's age is a real trust signal, that is a strange omission.
Fortunately, the creation date is not actually hidden. It is embedded in the server's ID, and decoding it takes about thirty seconds. The same trick works for channels and even individual messages. Here is the whole process, plus the situations where checking a server's age genuinely matters.
The Quick Version
- Turn on Developer Mode (User Settings, then Advanced, then toggle Developer Mode).
- Right-click the server's name or icon and choose Copy Server ID.
- Paste the ID into our snowflake converter to see the exact creation date and time.
That is it. The rest of this guide covers each step properly, explains why a server's ID contains its own birthday, and looks at what server age can and cannot tell you.
Step 1: Enable Developer Mode
Developer Mode is a simple toggle that adds "Copy ID" options to Discord's menus. It changes nothing else about the app.
On desktop: open User Settings with the gear icon next to your username, scroll to Advanced in the left sidebar, and switch Developer Mode on.
On mobile: open your app settings and find Developer Mode under the Advanced section. Discord has moved its mobile settings around over the years, but the toggle has stayed under Advanced.
You only need to do this once per device.
Step 2: Copy the Server ID
On desktop, right-click the server's icon in the server list on the far left, or click the server name at the top of the channel list to open its dropdown menu. Either way, choose Copy Server ID. It sits at the bottom of the menu.
On mobile, long-press the server's icon in your server list, or open the menu from the server's name, and look for Copy Server ID.
You will get a number 17 to 19 digits long, containing nothing but digits. That is the server's snowflake ID, and its creation timestamp is baked into it. Note that you do not need to be an admin or moderator: any member of a server can copy its ID, which is exactly what makes this useful for vetting communities you have just joined.
If you want a full walkthrough of copying every ID type Discord offers, see our guide on how to get any Discord ID.
Step 3: Decode the ID
Paste the ID into our snowflake converter. It shows the exact date and time the server was created, down to the millisecond, converted to your local timezone.
The lookup happens entirely in your browser. There is no login, nothing gets stored, and the tool never needs to contact Discord, because the date is encoded in the number itself.
Why a Server's ID Contains Its Creation Date
Discord IDs are snowflakes: 64-bit identifiers in which the top 42 bits store a creation timestamp, measured in milliseconds since January 1, 2015 at 00:00:00 UTC (the Discord epoch). Every user, server, channel, message, and role receives one at the moment it is created, and the timestamp portion never changes afterwards.
That means the ID doubles as a permanent birth certificate. No admin setting can alter it, transferring ownership does not reset it, and renaming or rebranding the server does not touch it. Shift the ID right by 22 bits, add the epoch, and you have the exact creation time. Our converter does the math for you.
The same principle dates user accounts, which is often the natural follow-up check: our account creation date guide covers that version of the trick step by step.
Channels and Messages Work Too
Because every Discord object carries a snowflake, the technique is not limited to servers.
Channels: right-click any channel and choose Copy Channel ID. Decoding it tells you when that specific channel was created. Here is a useful detail: the channels generated automatically when a server is first set up carry timestamps within moments of the server itself, so the oldest surviving channel is usually a close proxy for server age. If a server's oldest channel is dramatically newer than the server ID claims, the original channels were deleted at some point. That can be an innocent reorganization, or a sign the server was purged and repurposed.
Messages: every message has an ID as well (right-click the message, or use its three-dot menu, and choose Copy Message ID). Decode it and you know exactly when it was posted. That is occasionally valuable for pinning down when an announcement, rule, or claim actually appeared, independent of what anyone remembers.
Users: the same mechanics date any account, which pairs naturally with server checks when you are evaluating who runs a community.
Why People Check Server Age
Verifying a server's claimed history
"Established 2018" is an easy thing to type into a server description. The server ID settles the question in seconds. If a community advertises years of history but its ID decodes to three months ago, either the community migrated from an older server (which legitimate ones will usually explain when asked) or the track record is invented. This single check filters out a surprising amount of nonsense.
Vetting "official" servers
Impersonating the official server of a game, crypto project, or brand is a standard scam pattern. The fakes can copy the icon, the channel layout, the emoji, and the announcement style. What they cannot copy is age. The genuine official community for a product launched in 2020 will typically have a server ID from around that era, while a lookalike created two weeks ago answers its own question. Age is not proof on its own (also check for Discord's verification badge and links from the official website), but a very young ID on a server claiming long-established official status is a serious red flag.
Partnership and moderation diligence
If you run a server of any size, you will eventually receive partnership offers, ad swaps, and affiliate pitches from other communities. Checking the requesting server's actual age, and the account age of the person asking, is basic due diligence that takes under a minute. Fresh servers dressed up as established networks rarely survive it.
Curiosity and milestones
Sometimes you just want to know. Anniversary events, "the server turns five" announcements, or settling an argument about which of two communities is older: the ID answers all of it with millisecond precision.
What Server Age Can and Cannot Tell You
The decoded timestamp is exact and impossible to fake, but interpret it with some care.
- The ID never changes, no matter what the server becomes. Renames, new icons, ownership transfers, and total rebrands all keep the original ID. The date always refers to the moment of creation, not to the current community. This cuts both ways: an old ID is not proof that the current community, owners, or purpose are old, because servers can be bought and repurposed precisely so the age looks credible.
- Old does not mean trustworthy. If a server's ID is old but its channels all decode to last month, the content was wiped and rebuilt. That combination deserves a closer look before you trust it.
- Young does not mean bad. Every server was new once. Age only matters when it contradicts a claim someone is making.
Treat the creation date as one strong, unfakeable data point, and combine it with the softer signals: who the admins are, how old their accounts are, and whether official channels elsewhere link back to the server.
Common Questions
Can I check a server I haven't joined?
You need to be able to see the server in your client to copy its ID, so in practice you either join it (you can leave immediately afterwards) or get the ID from someone who is already a member. An invite code on its own does not show you the server ID.
Does the decoded time account for my timezone?
The timestamp inside the ID is stored in UTC, since it counts milliseconds from a fixed UTC epoch. Our converter translates it into your local timezone automatically, so the date and time you see match your own clock.
Can a server's creation date be wrong or spoofed?
No. The timestamp is generated by Discord's own infrastructure at the moment of creation and is part of the ID itself. There is no setting, bot, or API call that can modify it. If two tools disagree about a server's creation date, one of them is decoding incorrectly.
Does this work for group DMs and threads?
Yes. Group DMs and threads are channels under the hood, and channels have snowflake IDs like everything else. Copy the ID, decode it, and you have the moment it was created.
Try It
Copy any Server ID and drop it into our free snowflake converter. You will get the exact creation date and time instantly, and the same tool handles user, channel, and message IDs. No login, nothing stored, and all of the decoding happens locally in your browser.