Among Us hats: how cosmetics work, unlock rules, and seasonal sets
Among Us is a social deduction game built around a small, easily readable visual identity. The crewmate is a simple spacesuit, the color of the suit identifies a player at a glance, and the rest of the avatar’s character is built from a limited set of accessories. Among Us hats sit on top of that identity system. They do not change how the game plays, but they change how a player is read in a lobby, and they often tell other players when someone bought the paid edition, when they joined the game, or which seasonal event the player is currently engaging with.
Because the cosmetic system is small and the player base is large, hats are also one of the most common sources of confusion in the community. Some hats are tied to the paid Steam edition, some to free mobile builds, some to holiday windows, and some to platform-specific purchases. This guide focuses on how the system is designed, what the verified source data says about unlocking seasonal hats, and where players and developers commonly misread the rules.
What Among Us hats actually are in the cosmetic system
Hats in Among Us are a cosmetic layer attached to the top of a crewmate model. They are not tied to gameplay outcomes. They do not change the hitbox, the visibility radius, or the way the visor renders. They are part of the same visual customization slot that also includes pets, nameplates, and skin colors, and the cosmetic IDs are stored on the player’s local profile rather than on a server account.
Because the cosmetics are a presentation layer and not a progression layer, the design intent is closer to a wardrobe than to an unlock tree. The team at InnerSloth added the hat system in late 2020 alongside pets, and the goal was to give returning players a small reason to log in during the game’s second wave of popularity. The fact that hats are mostly visual is also why they are the most flexible category to manipulate through settings such as the device clock, which the verified Inverse guide covers in detail for the Christmas 2018 set.
For modders and developers looking at the structure, hats behave like a small lookup table:
- Each hat has a stable internal string ID used by the game’s assets.
- The ID is paired with a localized display name and a thumbnail used in the wardrobe menu.
- Each hat has at least one unlock condition, which can be a purchase flag, a date window, or a bundled release.
- A hat’s visibility in the wardrobe depends on the unlock condition being met on the local client.
This is important because the same hat can be visible to one player and hidden from another, even in the same lobby. The cosmetic check is client-side, so it reflects what the local game believes about its own ownership, not a shared server-side inventory.
How Among Us hats unlock on PC, iOS, and Android
Unlocking among us hats is mostly a function of three things: which edition of the game you own, what platform you bought it on, and which seasonal window the cosmetic belongs to. The verified Inverse source confirms this split directly: the $4.99 Steam edition unlocks nearly every hat by default, while the free mobile builds only include a more limited set, and seasonal hats are time-gated regardless of edition.
This creates three different experiences for a single cosmetic:
- Steam paid owners usually see the full wardrobe minus seasonal content.
- Free mobile players see a smaller set, and several hats are replaced with a buy prompt.
- All players see seasonal content appear and disappear based on a date check that the client performs against the device clock.
That last point is the one most often missed. A hat is not unlocked by paying for it during a holiday window. The client checks the system date, and if the device date falls inside the seasonal window, the hat becomes visible in the wardrobe. The Inverse guide describes exactly this mechanic in its Christmas 2018 example: changing the Windows clock to December 24, 2018 makes the skins appear, the same way time traveling in Animal Crossing: New Horizons exposes seasonal content early.
The role of the device clock in seasonal among us hats
The device clock manipulation is the most misunderstood part of the system, and it is also the part with the clearest source evidence. According to the verified guide, the procedure is straightforward on each platform.
- On Windows 10, right-click the clock in the taskbar, choose Adjust date/time, open the Date and time tab, click Change under Change date and time, and set the date to a point inside the seasonal window.
- On Android, open the system Settings, navigate to the Date and Time section, and disable automatic time before manually setting the date.
- On iOS, the same flow applies through Settings, General, Date and Time, with automatic time disabled first.
What the device clock actually changes is the seasonal flag the client checks when it loads the wardrobe. The cosmetics are not downloaded on demand, they are already present in the local build. The unlock is a local permission rather than a download, which is why this method works on platforms that are usually locked down for purchases.
The catch is that on free mobile builds, the seasonal hat appears as a buy prompt rather than as an equippable item. The Inverse source states this directly: changing the date on a mobile device gives the player the option to buy the gear, but InnerSloth is not accepting payments for those hats at the time of writing, so a free mobile player cannot actually equip a seasonal cosmetic just by changing the date. Only players who already bought the hat during a prior seasonal window can equip it from a different date.
What the verified source actually says about Christmas hats
The verified Inverse article is specifically about the Christmas 2018 set, which is the earliest seasonal hat release for Among Us. Reading the source carefully gives a more accurate picture than secondary forum posts and YouTube videos.
| Claim | Supported by source | Notes |
|---|---|---|
| Steam paid edition unlocks nearly all hats | Yes | Excludes seasonal content |
| Free mobile editions have a more limited set | Yes | Reflects the original 2018 free mobile release |
| Seasonal hats are time-gated | Yes | Date check on the client |
| Date change can expose Christmas hats on PC | Yes | Method confirmed for Windows 10 |
| Date change unlocks Christmas hats on free mobile | No | Buy prompt appears but payment is not accepted |
| All seasonal hats are unlockable with a date change | Not stated | Only the Christmas 2018 set is covered |
The same article is also careful to note that the game was released by a three-person studio, InnerSloth, in 2018 and surged in popularity in mid-2020, which is useful context for understanding why the seasonal hat system uses local flags instead of a server-driven entitlement. The team was small, the game was small, and the unlock system is correspondingly simple.
How the cosmetic check fits into a multiplayer round
Because hats are client-side, the cosmetic check does not affect the simulation. Two players in the same lobby can see different wardrobes, and neither will be wrong about which hat their own character is wearing. This matters for a few practical reasons:
- Screenshots taken for evidence or clips only show what the local client rendered, not a shared source of truth.
- A hat that is unlocked on one device is not transferred to another device unless the player logs in with a profile that already owns it.
- Streamers who change their clock to display seasonal content do not grant the same content to their viewers, and they are not violating the simulation by wearing a hat their viewers cannot see.
For developers, this is also a useful design contrast. A more modern live-service game would treat cosmetics as a server-tracked entitlement with a token system and a shared inventory. Among Us uses a simpler model that prioritizes local performance and ease of patching over cross-device persistence, which is consistent with the small team size described in the source.
Where the system starts to break down
Simple systems are easier to patch, but they also accumulate edge cases, and among us hats have several. The most common edge cases for players are also useful failure modes for any developer looking at the system as a case study.
- A hat is equipped on one device but missing on another because the second device has not recognized the purchase yet.
- A seasonal hat disappears from the wardrobe after a system update resets the date, even though the player still owns the cosmetic.
- A player changes the system clock to a future date, then changes it back, and the wardrobe state is inconsistent until the client reloads.
- A free mobile player who never bought the game sees a buy prompt for a seasonal hat that cannot actually be purchased, leading to confusion about whether the cosmetic was ever available.
None of these are bugs in the simulation. They are predictable consequences of a cosmetic system that does not have a server-side authority. For developers, the lesson is that a client-driven cosmetic model is fine for small games but tends to confuse players as the catalog grows. The earlier a team introduces a server-side entitlement table, the easier it is to add platform parity, refund logic, and audit trails later.
Why the cosmetic system is split between paid PC and free mobile
Among Us launched on mobile as a free-to-download game with ads, then later landed on Steam as a paid title. The Inverse source confirms that the $4.99 Steam price unlocks nearly every hat, while the free mobile builds are restricted. This split is not just a marketing decision. It is also a design compromise that follows the platform norms of 2018.
| Platform | Edition | Cosmetic access | Reason |
|---|---|---|---|
| Steam | Paid | Full set minus seasonal | One-time purchase unlocks the catalog |
| Android | Free | Limited set, buy prompts for the rest | Free-to-play model with optional purchases |
| iOS | Free | Limited set, buy prompts for the rest | Matches Android parity |
| All platforms | Any | Seasonal content during date window | Date-driven flag, not tied to purchase |
The important takeaway for anyone designing a similar system is that the split is intentional, but it is not always obvious to the player. Many new players assume the hat system is a single inventory, and they are surprised when a hat they see in a stream is not visible on their own device. The source article’s detail about buy prompts that cannot actually be completed is a clear example of how a small edge case can become a recurring community question.
Cross-device behavior and profile transfer
Among Us does not use a single sign-on profile. Each device stores its own cosmetic flags. When a player buys a hat on Steam, the flag is written to that Steam install. When the same player logs into a fresh install of the free mobile build, the flag is not there, because the purchase is tied to the platform rather than to the player.
This is a common cause of confusion for new players who buy the game on one device and expect their full wardrobe to carry over. In practice, the wardrobe is per device, and any cross-platform play in a lobby only synchronizes gameplay state, not cosmetics. A player who switches from a Steam install to a free Android install will see the Android wardrobe, including the limited set and any buy prompts.
Common myths about among us hats
The community has built a number of working theories about the hat system that do not match the source material. A short list of the most common claims, with the actual evidence:
- Myth: Hats can be unlocked by a code or redeemable token. Reality: There is no verified code system for hats. The unlock is a purchase flag, a date flag, or a bundled release.
- Myth: Every seasonal hat can be unlocked with a date change. Reality: Only the Christmas 2018 set is confirmed in the source, and even then only on Windows 10 and only with a paid Steam install.
- Myth: Changing the device clock permanently unlocks the hat. Reality: The unlock is local. If the device date is moved back outside the seasonal window, the hat returns to its hidden state until the client re-checks the date.
- Myth: A free mobile player can buy seasonal hats during a date change. Reality: The buy prompt appears, but the source states that InnerSloth is not accepting payments for those hats, so a free mobile player cannot equip a seasonal hat they did not already own.
These myths are useful as case studies for any developer documenting a cosmetic system. The first version of the documentation is rarely the version that survives in the community, and a careful source like the Inverse guide is the cleanest way to keep the canonical record accurate.
What a developer can learn from the Among Us cosmetic design
Looking at the Among Us hat system as a small, deliberately simple piece of design is more useful than trying to copy it wholesale. The lessons that hold up in other projects include:
- Local cosmetic flags are fine for small, single-device games, but they start to leak as soon as a second device is involved.
- Time-based unlocks should always be checked against a server timestamp, not the device clock, when cross-device parity matters.
- A buy prompt for content that cannot be purchased is a design smell. If a seasonal item is not for sale, the wardrobe should not show a buy button.
- Documentation written for the community is part of the design, not a separate concern. The Inverse article is essentially a player-facing spec for the seasonal unlock path, and it carries more weight than a forum post.
For players, the most useful takeaway is that among us hats are a wardrobe layer, not a progression system, and the rules around them are short enough to read once and apply forever. For developers, the system is a reminder that simple cosmetic logic can be made more confusing than it needs to be when the boundary between client and server is left implicit.
Frequently asked questions
Do among us hats change anything in the game?
No. Hats are a visual layer only. They do not change hitboxes, vision, task speed, or any other gameplay mechanic. They are stored on the local client and only affect what the player’s crewmate looks like in the lobby and during rounds.
Why does a hat show up on one device and not another?
The unlock flag is stored per device and per edition. A hat bought on Steam is not automatically available on a free Android install, because the two installs are separate profiles. The client only checks what the local install believes it owns.
Can a free mobile player unlock among us hats by changing the date?
The verified source says the date change reveals a buy prompt for seasonal content, but InnerSloth is not accepting payments for those hats through the free mobile builds. A free mobile player who never bought the hat cannot equip it, even with a date change.
Is the Christmas 2026 hat set the only seasonal set that works with a date change?
That is the only set the verified source explicitly covers. The article describes the method for the 2018 Christmas hats on Windows 10, with a paid Steam install. Other seasonal sets have followed since 2020, but the specific behavior of each new set is not part of this source and would need its own verification.
Does changing the Windows clock break online play?
No. The client only uses the device clock to check the seasonal flag, not to time matchmaking or game state. Changing the clock is a local operation and does not affect the simulation, the lobby, or other players.
Are hats server-side or client-side?
Hats are client-side. The local client decides which hats are visible in the wardrobe, and the same hat can be visible to one player and hidden from another in the same lobby. There is no shared inventory for cosmetics.
Why does the Steam edition unlock so many hats while the mobile free build does not?
The Steam edition is a paid title, and the price is intended to include the full cosmetic set. The mobile free build uses a free-to-play model with optional purchases, and the catalog is smaller by design to leave room for the purchase path.
Can a streamer wear a hat that their viewers do not have?
Yes. Because the wardrobe is local, a streamer who changes the system clock can wear a seasonal hat that their viewers cannot equip. This is one reason it is worth checking the streamer’s device setup before assuming a cosmetic is publicly available.
Is there a way to recover a hat that disappeared after a patch?
If the hat is seasonal, the most common reason is that the patch re-checked the date flag and the device clock has moved outside the seasonal window. Setting the clock back inside the window, or waiting for the next seasonal window, is the documented recovery path. For non-seasonal hats, a fresh install of the paid edition is the simplest way to restore the full set.
Do among us hats affect performance or networking?
No. The hat layer is part of the cosmetic draw call and does not change the network model or the simulation tick rate. A player can equip any hat without affecting frame time, latency, or the behavior of the game round.
Leave a Reply