← All guides

Steam trade restrictions and CS2 Trade Protection: a troubleshooting guide

By BuySteamAccountsPublished Updated and sources checked

Start with the message Steam shows and the item affected. A restriction on your account, a delay on one item, and an unavailable Market listing can have different causes. For CS2, completed trades deliver items immediately, followed by seven days of Trade Protection. That protection is separate from the account rules that determine whether you can make a trade in the first place. [2]

Problem this solves
Trading is unavailable and several different restrictions could explain it.
What you can do afterward
Identify the relevant notice, separate account and item restrictions and compare overlapping waits.

First, find what is blocked

Before changing a password, removing an authenticator or adding money, write down three things: the action you attempted, the exact restriction message, and any date Steam displays. Keep a screenshot for your own records. A message about selling an item does not necessarily explain why a different trade failed.

  1. Inspect the item in your Steam inventory. Look for its tradable and marketable status, a date, or the Trade Protected shield. Check the particular item you intend to move; another copy of the same skin can have a different history.
  2. Check the affected feature. Open Trade Offers if the problem concerns an exchange, or the Community Market if it concerns buying or selling there. Read the restriction before proceeding with a transaction.
  3. List recent account changes. Include Guard activation, authenticator transfer or removal, password recovery, a new browser, a purchase and a trade reversal. Record dates rather than estimating from the age of the account.

Use those observations to choose the relevant section below. An item-specific date points toward the inventory rules. An account-wide message points toward the restriction table. A problem confined to the Market also calls for the purchase and limited-status checks.

Account restrictions: which event starts which clock?

These are Valve’s published durations. A duration is measured from its trigger, not from account creation or the day you first notice the problem. The general restrictions come from Steam’s restrictions reference [1]; the transfer rule comes from its authenticator instructions [3].

Account events and their documented restrictions
TriggerDurationEffect or exception
Steam Guard first enabled or re-enabled15 daysTrading and Market access require Guard; leaving it disabled also blocks access.
New device or browser7 daysApplies on that device. Exempt if the mobile authenticator has been enabled at least 7 days.
Mobile authenticator transferred2 daysTrade and Market restriction after the official transfer process.
Mobile authenticator removed15 daysTrade and Market restriction.
Forgotten password reset5 days; 30 after over 2 months without activityTrade and Market restriction. Changing a known password is different.
Accepted trade cancelled during a hold7 daysTrading restriction; distinct from reversing a protected CS2 trade.

Treat “move,” “remove,” and “sign in” as different actions. Moving an authenticator using Steam’s transfer flow is not the same as removing it and setting it up again. Likewise, authorizing a browser is not an authenticator transfer. Read the confirmation screen before committing to an account change.

If you suspect somebody else has access, secure the account even if that interrupts trading. Use the account security and recovery guide to plan the steps from a secure device. Protecting a trading deadline is not a reason to leave a compromised login active.

CS2 items arrive immediately, then receive Trade Protection

Valve’s CS2-specific rule supersedes generic advice about trade escrow: CS2 items are not held before delivery. After a completed trade, they remain protected for seven days. You can equip them, but cannot transfer, consume or modify them, including moving them into a Storage Unit. An older account or mobile authenticator does not shorten that period. [2]

During that window, eligible trades can be reversed from Trade History after you regain control of the account. Reversal affects all eligible protected trades from the previous seven days, not just one selected item. The initiating account receives a 30-day trade and Market cooldown; its trade partners do not receive that cooldown. Once protection expires, the trade cannot be reversed through this feature. [2]

For planning, keep two dates: when an item arrived and when Steam says it can move again. Do not schedule an onward sale merely because the first trade is complete. If a marketplace also delays settlement, put that date in your plan separately. Read the reversal preview carefully before confirming it so you understand the other trades affected.

Separate trade escrow from Market-listing holds

Steam’s general authenticator documentation describes holds on trades and Market listings created before a mobile authenticator is added or during its first seven days. Those holds can last up to 15 days, and adding an authenticator does not erase an existing hold. A trade hold delays an exchange; a Market-listing hold delays a sell listing becoming available to buyers. Check which action the hold notice names. [3] [6]

Valve’s CS2 exception removes trade holds and trade escrow for CS2 item exchanges. It does not establish an exemption from a separate Community Market listing hold. For a CS2 sale, read the listing’s own notice; do not apply the immediate-delivery rule for a completed trade to a listing awaiting release. This does not mean every CS2 listing has a hold. [2] [3]

Community Market access has additional requirements

The Market is the Steam feature where items are bought and sold for Steam Wallet funds. Its purchase requirement is separate from an exchange between accounts. Valve requires a successful qualifying purchase older than seven days but no more than a year old, alongside the Guard requirement. Wallet funds, games, DLC and software can qualify; activating a retail key or buying a gift does not satisfy this particular purchase rule. [4] [1]

A chargeback changes which purchases count. Valve considers only qualifying purchases made after the most recent chargeback for this purchase-history requirement. If the account has a chargeback, compare that date with the purchase you are relying on; an otherwise recent purchase from before it is insufficient. [1]

Limited accounts also lack Market access. Valve’s threshold is at least US$5 of qualifying spending or funding, with local purchases evaluated in USD. This is an account-status test, not a timer. The limited-account rules specifically mention Community items such as cards and gems and access to the Web API; they should not be shortened to “every CS2 trade needs a $5 purchase.” [5]

A new unverified payment method can additionally cause a three-day wait for Market purchases. Steam offers verification for supported cards; that process does not remove unrelated restrictions. Read the payment message before assuming that another top-up will solve it. Items bought on the Market or in-game may also have their own availability date. [4] [1]

Worked examples: overlapping clocks

These are planning examples, not promises about an individual account. Use elapsed time and the timestamp Steam displays. A calendar date alone can be misleading near an expiry.

An established account changes phones

Suppose Guard and the mobile authenticator have been active for months. On Monday at 14:00 you complete Steam’s authenticator transfer. In isolation, the two-day transfer restriction points to Wednesday at 14:00. Now suppose you reset a forgotten password on Tuesday at 10:00. The five-day reset period points to Sunday at 10:00 instead, assuming the account was recently active. Finishing the first restriction does not finish the second.

A new account is being prepared for the Market

Suppose Guard is enabled on day 0 and a successful $5 Wallet purchase is made on day 10. On day 15, the Guard period has elapsed, but the purchase is only five days old. For the purchase-age requirement, plan beyond day 17 at the purchase’s original time. Before using the Market, also check limited status, payment restrictions and any item-specific date. Waiting 15 days from creation would miss the later purchase clock.

An item arrives while you can already trade

Suppose an otherwise eligible account receives a protected skin on Tuesday at 18:00. Other eligible inventory may remain usable, but that skin has its own seven-day protection period. Track the item’s displayed availability rather than diagnosing the whole account as blocked. An account restriction imposed later could still delay its next transfer.

A practical next-step checklist

  • Keep the exact error and affected item together in your notes.
  • Match each recent account event to its own expiry; do not add overlapping timers end to end.
  • Check Market eligibility separately if buying or selling there is your objective.
  • Recheck the item and account messages after the latest relevant expiry.
  • If Steam identifies a ban, lock or security issue, use the appropriate Support route instead of assuming it is a routine wait.

Steam Support says it cannot modify these trading and Market restrictions. [1] For a blocked account rather than a routine timer, read what locks and bans mean for a CS2 inventory. If you are preparing an account from scratch, the account age and eligibility checklist helps you record the requirements before setting a date.

Sources and review notes

The primary sources below were checked on September 9, 2026. Use Steam’s current screens and the linked guidance to check the conditions that apply to your account or transaction. Worked examples are illustrations; they do not inspect an account or provide live market quotes.

  1. Steam Support: Trading and Market Restrictions
  2. Steam Support: Trade Protected Items
  3. Steam Support: Steam Guard Mobile Authenticator
  4. Steam Support: Community Market FAQ
  5. Steam Support: Limited User Accounts
  6. Steam Support: Trade and Market Holds
Back to top ↑

Yandex analytics

Yandex Metrica helps us count visits to public website pages and discover updated pages. Yandex receives the public page address and basic request, browser and device information, including your IP address, and may use analytics cookies.

We exclude account dashboards, sign-in, checkout, API and other private pages. We remove query strings and fragments from page addresses and do not send document titles, original referring-page addresses, form contents, credentials, orders or account identifiers.

Session replay, click maps, link tracking, ecommerce and automatic goals are disabled. Optional vendor features and diagnostic requests are blocked by this site’s security policy.

Your choice is saved in this browser. Global Privacy Control and Do Not Track also disable Yandex analytics. This control applies only to Yandex Metrica; it does not change Google Analytics or other services on this site.

Yandex analytics is enabled for public pages in this browser.