How to File ITR for Gaming Income: 2026 Step-by-Step Guide

The 30-second answer

For FY 2025-26 online gaming winnings — including a gaming TDS refund claim — use ITR-2 (or ITR-3 with business income), never ITR-1. Report net winnings on the 115BBJ line of Schedule OS, claim the 30% TDS in Schedule TDS2 via each operator’s TAN matched to Form 26AS, e-verify within 30 days, and file by 31 July 2026.

This page is a sourced filing walkthrough, not tax advice. Every form name, schedule, section number and deadline below is tied to the Income-tax Act, CBDT notifications, the e-filing portal, or a named tax source. It shows you the mechanics of putting gaming winnings into your ITR and claiming the TDS. It does not replace a chartered accountant for your specific return, and it is not written by a tax professional. For a filing decision that affects your money, talk to a qualified CA.

Who this is for, in one breath. You had online gaming winnings in FY 2025-26 — from a fantasy app, a rummy or poker platform, or a Teen Patti game — the operator took roughly 30% before paying you, and now a gaming entry is sitting in your AIS and you have to file a return that reconciles to it. This page is the end-to-end “how do I actually do it” guide: which form, which boxes, where the numbers come from, and how to make the TDS line up so your refund or balance computes right. The law behind the 30% — Section 115BBJ, the net-winnings formula, the 28% GST — is explained in full on our online gaming tax India 2026 page; this page assumes you’ve read that or trust the numbers, and gets straight to filing.

The PROGA wrinkle you must read first. The Promotion and Regulation of Online Gaming Act, 2025 (PROGA) banned online money games, and the big operators suspended cash play from late August 2025. That does not erase your tax filing. Any winnings you booked between 1 April 2025 and the shutdown — plus any wind-down recovery payout of a stranded balance — are taxable in FY 2025-26 and must appear on the return you file in 2026. A discontinued app does not mean a discontinued tax obligation. If your recovery payout arrived about 30% lighter, that’s TDS, it’s in your 26AS, and this page shows you how to claim it back. If you’re still chasing that stranded balance, start at our gaming TDS refund claim page first, then come back to file.

Before you start: the five things to gather

Filing goes fast when the inputs are ready and slowly when you’re hunting for a TAN at 11pm on 31 July. So the very first job is assembling five documents. Get these five in front of you and the rest of this page is data entry.

1. Your PAN — the same PAN that is registered on every gaming account you played. If your gaming account carried a different or old PAN, the TDS landed in the wrong 26AS and you cannot claim it. Fix that mismatch with the operator before you file, not after.
2. Form 26AS — your consolidated tax-credit statement, pulled from the income-tax e-filing portal. This is the official record of how much 194BA TDS was deducted against your PAN, by which operator, in which quarter. You can only claim what shows here.
3. AIS and TIS — the Annual Information Statement and its summarised cousin, the Taxpayer Information Summary. The AIS lists your gaming winnings as a reported transaction; the TIS rolls them into a processed total. The department already has this data, so your return must match it.
4. Each operator’s Form 16A — the quarterly TDS certificate for the 194BA deduction. This is your document-level proof and your reconciliation anchor when 26AS and AIS disagree.
5. Your own deposit/withdrawal record — the operator’s transaction history or a CSV export, so you can rebuild the net-winnings figure yourself and check it against what the app reported. Five minutes of arithmetic here saves a notice later.

The pre-flight rule: before you open the ITR utility, have your PAN, Form 26AS, AIS/TIS, every operator’s Form 16A, and your own deposit/withdrawal history in one folder. Filing is just transcription once these five agree with each other — and reconciling them before you file is the single best defence against a mismatch notice.

The order of the rest of this page follows the order you’ll actually do the work: pull and read your 26AS/AIS/TIS, rebuild net winnings, decide whether you even have to file, pick the form, fill Schedule OS, fill Schedule TDS2, let the system compute, pay any balance, e-verify, and watch the deadlines. A full worked example runs end-to-end at the bottom. There’s a section for the in-kind prize case, one for the no-deduction rules as they bite in the form, and one for the PROGA wind-down filing specifically.

Step 1 — Pull and read your Form 26AS, AIS and TIS

You do not file from memory or from the app’s screen. You file from the three official statements the department maintains against your PAN, because those are the numbers the system will validate your return against. All three sit behind your login on the e-filing portal.

Form 26AS — your tax-credit statement

Form 26AS is the record of tax already paid in your name. When a gaming operator deducts 194BA TDS, it files a TDS return quoting your PAN and its own TAN (Tax Deduction Account Number), and that deduction flows into your 26AS, split by quarter (ClearTax on viewing 26AS). Open 26AS and you will see, for each operator: the deductor’s name and TAN, the amount paid/credited, and the TDS deducted. Write down each operator’s TAN and TDS figure now — you will key both into Schedule TDS2, and the TAN is the part people forget to capture and then have to dig back out.

A practical detail: a single operator can appear as multiple lines in 26AS, one per quarter, because TDS is reported quarterly. Add the four quarters to get that operator’s annual TDS, but keep the quarter split, because Schedule OS will ask for winnings quarter-by-quarter too.

AIS — the Annual Information Statement

The AIS is broader than 26AS. It captures not just TDS but the transactions reported against your PAN — including winnings from online games as a specified information category (G2G News on ITR reporting). This is the statement that turns “I’ll just not mention it” into a notice. The operator reported your winnings; the AIS surfaced them; a return that omits them no longer matches the department’s data. Treat the AIS figure as the department already knowing your number, because it does.

TIS — the Taxpayer Information Summary

The TIS is the AIS, summarised. It takes the raw AIS line items and presents a processed value per category — so your online-gaming winnings appear as a single rolled-up figure the system is inclined to treat as your reportable number. If you submit feedback on an AIS line (say, to flag a duplicate), the TIS recomputes. So the TIS is the “what the department thinks the right total is, after your corrections” view. Read it last, after you’ve reconciled the AIS.

The three-way reconciliation that prevents notices

Before you key a single figure into the form, run this check, because nine out of ten gaming-tax notices trace back to skipping it:

1. From AIS/TIS: note the total online-game winnings reported against your PAN.
2. From Form 26AS: note the total 194BA TDS credited, broken out by deductor and quarter.
3. From each operator’s Form 16A: confirm the per-platform TDS rolls up to the 26AS total.

If the AIS winnings figure looks too high — a real and recurring problem is operators reporting gross figures or duplicate entries — you do not quietly drop it. You report correctly and use the AIS feedback facility to flag the discrepancy, keeping your operator statements and bank credits as evidence for the corrected figure. If the TDS in 26AS is lower than what an operator’s Form 16A says it deducted, chase that operator to file or revise its TDS return, because you can only claim the TDS that appears in 26AS. An unreconciled mismatch is the number-one trigger for a defective-return or under-reporting notice in this category.

Step 1 in one line: your winnings live in AIS/TIS and your 194BA TDS lives in Form 26AS (with each operator’s TAN), and each operator’s Form 16A is the per-platform proof. Make all three agree before you open the form — claim only the 26AS TDS, report winnings consistent with AIS, and flag genuine AIS overstatements through feedback rather than ignoring them.

Step 2 — Rebuild your net winnings under Rule 133

The number you report is net winnings, not gross winnings and not the headline figure on the app. The law explainer covers the full mechanics; here is the part you actually need to compute your figure for the form. The formula, set by Rule 133 of the Income-tax Rules, is the same for every platform:

Net winnings = (A + D) − (B + C)

where, per Rule 133:

• A = total amount withdrawn from your account on the platform during the financial year,
• B = total non-taxable deposits you made into the account during the year,
• C = opening balance of the account on 1 April 2025,
• D = closing balance of the account on 31 March 2026.

In plain words: you are taxed on (what came out + what’s still sitting there) minus (what you put in + what was already there) — your genuine yearly profit on that app. Compute it per platform, and floor each platform’s result at zero. A platform where the formula goes negative produced no taxable winnings, but — and this is the rule that hurts — that loss does nothing for you elsewhere.

Why you rebuild it yourself even though the app reported a number

You compute net winnings yourself for one reason: to catch the case where the app’s reported figure is wrong, inflated, or double-counted. The operator’s Rule 133 number lives in its records (including bonus accounting and previously-taxed carry-forwards you may not be tracking), so your back-of-envelope sum and the app’s figure can legitimately differ. When they differ, you reconcile to the operator’s Form 16A and your 26AS, and you use AIS feedback if the reported figure is genuinely overstated. But you can only know it’s overstated if you did the arithmetic. So do it.

A two-platform worked computation

Say you played on two apps in FY 2025-26 before they wound down:

• App A (fantasy): deposits ₹50,000 (B), withdrawals ₹85,000 (A), opening ₹0 (C), closing ₹0 (D). Net winnings = (85,000 + 0) − (50,000 + 0) = ₹35,000.
• App B (rummy): deposits ₹80,000 (B), withdrawals ₹50,000 (A), opening ₹0, closing ₹0. Net winnings = (50,000 + 0) − (80,000 + 0) = −₹30,000 → floored to ₹0.

Your total taxable gaming winnings = ₹35,000 + ₹0 = ₹35,000. App B’s ₹30,000 real loss is dead for tax — no set-off against App A, no carry-forward. Your real economic result across both apps was ₹5,000 of profit, but the figure you report is ₹35,000. That gap is the no-set-off rule, and it shows up in the form exactly as harshly as it sounds. We come back to why the ITR utility itself enforces this in the schedule sections below.

Step 2 in one line: report net winnings = (withdrawals + closing balance) − (your deposits + opening balance), computed per platform and floored at zero, totalled across platforms. Rebuild it yourself from your transaction history so you can catch an inflated AIS figure — but reconcile to the operator’s Form 16A / 26AS when your number and theirs differ.

Step 3 — Do you even have to file? The thresholds

Some players assume that because TDS was already deducted, the obligation is over. It is not — and several rules make filing mandatory even when you’d otherwise be below the basic exemption.

The “TDS already deducted” trap

The biggest misconception in this whole category: TDS is an advance, not the final tax. The operator took 30% and paid it to the government against your PAN. Your actual liability under Section 115BBJ is 31.2% (30% + 4% cess), and the only way the 30% already paid gets credited — and the only way any over-deduction comes back as a refund — is by filing a return. Skipping the ITR because “they already took the tax” leaves your AIS showing winnings against a non-filed return, which is the classic notice trigger. So the deduction does not remove the filing duty; it creates one.

The income thresholds and the special rule that overrides them

Two threshold rules matter here, and the second one surprises people:

• Basic filing threshold. Normally you must file if your total income exceeds the basic exemption limit. But gaming winnings taxed at the special 115BBJ rate are part of total income, and even a person whose only income is gaming winnings can be pushed over the line — there is no basic-exemption shelter for the gaming portion. A student with ₹0 salary and ₹40,000 of net winnings owes 30% on the ₹40,000 and should file.
• The Rule 12BA TDS trigger. Separately, Rule 12BA makes filing compulsory if your aggregate TDS/TCS in the year exceeds ₹25,000, regardless of your income level (CAalley summary). So a player whose gaming TDS alone crossed ₹25,000 — which happens at roughly ₹83,000 of net winnings — must file even if their total income is otherwise below the exemption limit. The deduction you suffered can itself be the thing that forces the return.

The honest summary on “must I file”

If you had online gaming winnings in FY 2025-26, the safe and almost-always-correct answer is yes, file. You file to claim the TDS credit, to avoid the AIS-mismatch notice, and frequently because Rule 12BA or the no-exemption rule makes it mandatory anyway. The only realistic “no” is a tiny win where no TDS was deducted, no AIS entry exists, and your total income is genuinely below the exemption limit — and even then, filing costs you nothing and forecloses a notice.

Step 3 in one line: file. TDS deducted ≠ tax done; the credit and any refund only come through a return. Gaming winnings get no basic-exemption shelter, and Rule 12BA makes filing mandatory once your aggregate TDS/TCS exceeds ₹25,000 — which gaming TDS alone can breach at around ₹83,000 of net winnings.

Step 4 — Pick the right ITR form (never ITR-1)

The form you use depends on the rest of your income, not on the gaming income itself. But the gaming income does one thing decisively: it knocks out ITR-1.

ITR-2 — the form most players use

Use ITR-2 if you are salaried, a pensioner, or have capital gains, and your only “other” income is winnings — that is, you have no business or professional income (G2G News). This is the form the typical gaming player files. ITR-2 has the Schedule OS with the dedicated Section 115BBJ line and the Schedule TDS2 you need to claim the 194BA credit, so everything in this guide maps onto it.

ITR-3 — if you have business income

Use ITR-3 if you have business or professional income alongside (or instead of) gaming winnings — for example, you’re self-employed, run a shop, or have professional receipts. ITR-3 carries the same Schedule OS and Schedule TDS2, so the gaming-specific steps are identical; you just attach them to a business return. Note that for the ordinary player, gaming winnings are Income from Other Sources, not business income — you only use ITR-3 because of your other activity, not because gaming made you a “business.”

Why ITR-1 (Sahaj) is off the table

ITR-1 cannot handle income taxed at the special 115BBJ rate. It is built for simple salary-and-one-house-property situations and has no field for winnings charged at the flat special rate. A salaried player with gaming winnings who files ITR-1 has filed a defective return, which the department can flag and which then has to be corrected. So the moment you have online gaming winnings, ITR-1 is gone — drop to ITR-2 at minimum, or ITR-3 if business income is in the picture (reporting guidance).

A quick decision table

Step 4 in one line: never ITR-1. Use ITR-2 if you have no business income (salaried, pensioner, or capital gains), and ITR-3 if you have business or professional income. The size of the winnings is irrelevant — it’s the special 115BBJ rate that rules out the simple form.

Step 5 — Report winnings in Schedule OS (the 115BBJ line)

Online gaming winnings are taxed under the head Income from Other Sources, so they go in Schedule OS. But not just anywhere in Schedule OS — there is a dedicated line for income chargeable under Section 115BBJ, “winnings from online games,” and that is where your figure goes.

The exact field

Inside Schedule OS, find the line for income by way of winnings from online games chargeable under Section 115BBJ. Enter your net winnings here — the Rule 133 figure from Step 2, totalled across platforms (each platform computed independently, losers floored at zero). This line is separate from the older Section 115BB line that handles traditional lottery and game-show winnings, so don’t confuse the two: online games go on the 115BBJ line; lotteries and TV game shows go on the 115BB line. Putting your gaming winnings on the wrong line, or in the generic “other income” box, defeats the purpose — the dedicated line is what applies the flat 30% instead of your slab rate.

The quarter-wise break-up

The form also asks for a quarter-wise break-up of these winnings (reporting guidance). This is why you kept the quarterly split from 26AS in Step 1. Split your net winnings across the four quarters according to when they accrued — roughly, when you withdrew or when the year-end sweep hit. The quarter split feeds the system’s interest computation (it affects how advance-tax interest under the relevant sections is calculated), and the four quarters must sum to your annual figure, or the utility throws a validation error. For a PROGA player whose winnings all landed before the late-August 2025 shutdown, expect everything to fall in Q1 (Apr–Jun) and Q2 (Jul–Sep), with little or nothing after — which is itself a clean way to sanity-check your split.

The “no negatives” rule the utility enforces

A subtle but important point: the ITR utility does not allow a negative figure in the dedicated online-gaming field of Schedule OS. You cannot enter App B’s −₹30,000 loss to net it against App A’s ₹35,000 win. The form itself bars it, which is the no-set-off rule enforced in software. So you enter ₹35,000, not ₹5,000, not ₹35,000 minus the loss. If your honest per-platform sum produced any negatives, they are already floored to zero before they reach this box.

How the figure flows to your tax

Once the net-winnings figure is on the 115BBJ line, the system taxes it at the flat 30% plus 4% cess (= 31.2%), outside your normal slabs. So even if your salary sits in a 5% or 20% bracket, the gaming portion is taxed at 30%. There are no deductions against it (no 80C, no 80D), no set-off of losses, and no basic-exemption shelter — all of which we detail in the dedicated rules section below, but which are worth knowing as you type the number in, so you don’t expect the form to reduce it. It won’t.

Step 5 in one line: enter your net winnings on the Section 115BBJ line of Schedule OS (not the 115BB lottery line, not the generic other-income box), with the quarter-wise split that sums to the annual figure. The utility bars negatives, so each platform’s positive net winnings go in at full value — the form taxes them at a flat 31.2% outside your slab.

Step 6 — Claim your TDS in Schedule TDS2

This is the step that turns the 30% you already lost into a credit against your final tax. Skip it or mis-key it, and you pay tax twice on the same winnings. Get it right, and you either owe a small balance or collect a refund.

What goes in Schedule TDS2

The TDS deducted on non-salary income is claimed in Schedule TDS2 (“TDS on income other than salary”). For each operator that deducted 194BA TDS, you enter:

• the TAN of the deductor (the operator) — exactly as it appears in your 26AS,
• the gross amount paid/credited, and
• the TDS deducted,

all matched to your Form 26AS figures. The TAN is non-negotiable: the credit is keyed to it, and an operator with no valid TAN entry in your 26AS gives you nothing to claim. If you played on two operators, you enter two rows — one per TAN — even though both feed the same Schedule OS line.

Match it to 26AS, then verify against Form 16A

The portal’s pre-fill usually populates Schedule TDS2 from your 26AS automatically. Do not trust it blindly — verify every line against your own Form 16A figures before you submit. Two failure modes to watch:

• A figure in your Form 16A that is missing from 26AS. You can claim only what 26AS shows. If the operator deducted but hasn’t filed (or filed wrong), the credit isn’t in 26AS yet, and claiming a number that isn’t there causes a credit mismatch. Chase the operator to file or revise its TDS return before you file yours, or file with the credit you can prove and revise later.
• Higher-than-30% deduction from a missing PAN. If a valid PAN was not furnished to the operator, TDS can be deducted at a higher rate under the rules for missing PAN. Recovering that excess depends entirely on filing — so a player who let an account run without a verified PAN has a bigger credit to claim and absolutely must file to get it back.

Why this is where refunds happen

Because 194BA deducts a flat 30% at source while your final liability can sometimes be lower, refunds arise — typically when the TDS was over-deducted (gross or duplicate reporting later corrected) or you have excess credits from other sources. But manage expectations: for a straightforward net winner, the 30% TDS is slightly less than the 31.2% final tax, so the usual outcome is a small top-up, not a refund. The refund scenario is the exception. The full mechanics of when and how a refund actually comes back — including the over-deduction and wind-down cases — are walked through on our gaming TDS refund claim page; here, the point is just that Schedule TDS2 is the box that makes it possible.

Step 6 in one line: claim the 194BA TDS in Schedule TDS2 — one row per operator TAN, with the gross amount and TDS matched to Form 26AS, verified against each Form 16A. You can claim only what 26AS shows; this box converts the 30% already taken into a credit, and in over-deduction or missing-PAN cases it’s where a refund is unlocked.

Step 7 — Let the system compute, then pay any balance

With winnings on the 115BBJ line of Schedule OS and TDS in Schedule TDS2, the e-filing utility does the arithmetic. You don’t compute the tax by hand; you check that its output makes sense.

What the system does

The utility taxes your net winnings at 30% + 4% cess = 31.2% (plus surcharge only if your total income exceeds ₹50 lakh), outside your salary slab, then subtracts the TDS credit from Schedule TDS2. Two outcomes:

• A small balance to pay. The common case for a net winner: the 30% TDS didn’t cover the extra 4% cess, so a small top-up remains. On ₹35,000 of winnings, the cess gap is roughly ₹420. You pay this as self-assessment tax before filing.
• A refund. If your TDS exceeded your final liability (over-deduction, correction, or excess credits elsewhere), the system computes a refund to your registered bank account.

Paying the self-assessment top-up

If a balance is due, pay it through the e-Pay Tax facility on the portal before you submit the return, and enter the challan details so the payment is reflected. A return filed with an unpaid self-assessment balance is defective. The top-up is usually small — for most net winners it’s the cess the flat 30% TDS didn’t reach — but it has to be cleared for the return to be valid.

A sanity check on the number

Before you accept the computed tax, do a one-line check: net winnings × 31.2%, minus your 26AS TDS, should roughly equal the balance the system shows on the gaming portion. If the system’s gaming tax is wildly different, you’ve probably keyed the winnings on the wrong line (slab rate instead of 115BBJ) or mismatched the TDS. Catch it here, in the preview, not after a notice.

Step 7 in one line: the utility taxes net winnings at 31.2% outside your slab and credits the Schedule TDS2 TDS. A net winner usually owes a small cess top-up (≈₹420 on ₹35,000), paid as self-assessment tax via e-Pay Tax before filing; over-deduction produces a refund. Sanity-check with winnings × 31.2% − 26AS TDS.

Step 8 — Submit and e-verify within 30 days

Filing isn’t finished when you click submit. A return that is submitted but not verified is treated as not filed at all — and the verification window is tight.

The 30-day e-verification rule

After you submit, you must e-verify within 30 days. A filed-but-unverified return is invalid, as if you never filed — which means if the 30 days lapse past the deadline, you’ve effectively missed the deadline and slid into belated territory. So verify immediately after submitting; don’t leave it for “later.” E-verification is mandatory to complete the process, and it applies equally to belated returns filed under Section 139(4).

How to e-verify

The fastest route is the Aadhaar OTP — the portal sends a one-time password to the mobile linked to your Aadhaar, you enter it, and the return is verified in seconds. Other options include net-banking, a pre-validated bank-account or demat-account EVC, or the old paper route of mailing a signed ITR-V to CPC Bengaluru (slow, avoid it if you can OTP). For a gaming return you want done cleanly, Aadhaar OTP at the moment of submission is the path that closes the loop and starts processing.

Why this matters for your refund

If your return produces a refund (the over-deduction case), the refund only processes after verification. An unverified return sits in limbo — no credit, no refund, and the clock running toward “not filed.” So the discipline is simple: submit, then verify in the same sitting. The 30-day window is a grace period, not a plan.

Step 8 in one line: a submitted but unverified return counts as not filed, so e-verify within 30 days — ideally the instant you submit, via Aadhaar OTP. Verification is what starts processing and releases any refund; the 30 days is a grace window, not a habit to lean on.

Deadlines and what late filing actually costs

The dates are not negotiable, and missing them is expensive in ways beyond the obvious fee. Here is the calendar for AY 2026-27 and the real cost of slipping.

The key dates

• 31 July 2026 — the original due date for individual (non-audit) returns for FY 2025-26. Almost every gaming player files in this category.
• 31 October 2026 — the due date if your accounts require audit under Section 44AB (relevant only if you have a business that triggers audit; not the gaming income itself).
• 31 December 2026 — the last date to file a belated return under Section 139(4) for AY 2026-27, and the last date to file a revised return for the same year.

What it costs to file late

Miss 31 July and file belated, and you pay:

• A Section 234F late fee. ₹5,000 if your total income exceeds ₹5 lakh; reduced to ₹1,000 if total income is below ₹5 lakh; and nil if your income is below the taxable limit.
• Section 234A interest on any unpaid tax, accruing from the due date until you file — so a self-assessment top-up left unpaid grows.
• Lost loss-carry-forward rights — restrictions kick in on carrying forward business and capital losses if you file late. This rarely bites a pure gaming player (gaming losses can’t be carried forward anyway), but it matters if you have other losses to preserve.

The advance-tax angle most players miss

There’s a second clock besides the filing deadline: advance tax. If your total tax liability for the year (including the gaming portion the TDS didn’t fully cover) is ₹10,000 or more, you’re technically expected to have paid it in instalments across the year rather than as a lump at filing. For most gaming players the 30% TDS covers nearly all of it, leaving only the small cess top-up, so advance tax rarely bites. But a player who won a large amount on a platform that under-deducted (or won mostly in-kind without enough cash withheld) could carry a sizeable uncovered balance and accrue Section 234B and 234C interest for not paying advance tax on time. The quarter-wise winnings split you entered in Schedule OS feeds exactly this computation. If you suspect a big uncovered balance, pay it as advance tax before year-end rather than waiting for filing, to stop the interest from running.

The deeper risk for gaming income specifically

For gaming income there’s a sharper edge than the fee. Because your winnings are already in the AIS, a return that is late or never filed leaves a visible mismatch the department can act on — and tax authorities have signalled they will pursue real-money-gaming non-filers, with the possibility of notices and, in serious cases, prosecution for willful non-filing (CAalley). So the cost of being late on a gaming return is not just ₹5,000; it’s standing out in a category the department is actively watching. File on time.

The deadline summary: original due date 31 July 2026, belated and revised returns until 31 December 2026. Late filing costs a 234F fee (₹5,000, or ₹1,000 under ₹5 lakh income), 234A interest on unpaid tax, and lost carry-forward rights. For gaming income the bigger risk is the AIS mismatch a missing return leaves visible to a department that is actively pursuing real-money-gaming non-filers.

The no-deduction, no-set-off, no-exemption rules — as they bite in the form

These rules are the harshest feature of gaming taxation, and they’re explained in full on the legal tax page. What follows is the part that matters while you’re filling the form — because each rule shows up as something the ITR utility either refuses to let you do or silently ignores.

No deductions (the form gives you nowhere to put them)

You cannot reduce gaming winnings by:

• Chapter VI-A deductions — no 80C (PPF, ELSS, LIC), no 80D (health insurance), nothing. These deductions apply to your other income, never to the 115BBJ winnings line. The form structurally keeps them apart.
• Expenses — data, devices, subscriptions, “coaching.” There is no expense box against the winnings line because winnings aren’t business income. Rule 133 already subtracted your deposits inside the net-winnings formula; you get nothing beyond that.
• The basic exemption limit — the 30% applies from the first rupee of net winnings. The form does not net the basic exemption against this line. A person with ₹0 other income and ₹40,000 of winnings still computes 30% on the full ₹40,000.

No set-off (the utility bars the negative)

You cannot set off a loss on one platform against a win on another, and the utility enforces it directly: as noted, the online-gaming field in Schedule OS rejects a negative figure. So a ₹40,000 loss on App B literally cannot be entered to reduce a ₹50,000 win on App A — you report ₹50,000 and pay 30% on it. You also cannot set gaming losses against salary, business, or capital-gains income; the schedules don’t connect that way.

No carry-forward

A net gaming loss in FY 2025-26 cannot be carried forward to offset winnings in a future year. There is no schedule line to park it in, because the system doesn’t recognise a carry-forward of this loss type. The loss simply ends.

Why this produces a tax bill bigger than your real profit

The combined effect, seen in the form, is that your taxable winnings can exceed your actual net profit. The two-platform example from Step 2 makes it concrete: real profit ₹5,000, but the form taxes ₹35,000 because App B’s ₹30,000 loss has no box, no set-off, and no carry-forward. This isn’t a quirk you can engineer around in the utility — the form is built to enforce it. Knowing that as you file stops you from hunting for a deduction box that doesn’t exist.

The relief rules in the form: none. No Chapter VI-A or expense box against the 115BBJ line, no basic-exemption netting, and the Schedule OS gaming field rejects negatives so losses can’t offset wins — not across platforms, not against other income, and never carried forward. Your taxable winnings can legitimately exceed your real profit, and the utility is designed to make sure they do.

Filing when your winnings were partly in kind

Not every win is cash. Tournaments sometimes pay prizes as gadgets, vouchers, bikes, or convertible coins, and these are taxable — so they have to make it onto your return at the right value. This is the case players most often miss, treating a non-cash prize as “not real money.”

How an in-kind prize is valued

Under CBDT Circular 5/2023, winnings in kind are valued at fair market value (FMV), with two exceptions: if the operator bought the prize before giving it to you, the purchase price is the value; if the operator manufactures the item, the price it charges its customers is the value (CBDT guidelines summary). That value is the figure that enters your net-winnings computation and, ultimately, your Schedule OS line — a ₹60,000 phone won online is ₹60,000 of winnings, not zero.

The “ensure tax is paid before release” rule

Here’s the mechanism that affects you at the moment of the win. When net winnings are wholly in kind, or partly cash but the cash part is too small to cover the TDS on the whole, the operator must — before releasing the prize — ensure the tax has been paid on the net winnings. In practice that means you may have had to remit the TDS amount to the operator (or have it collected) before the gadget or voucher was handed over. So on a ₹60,000 phone with no cash alongside it, you would have paid roughly ₹18,000 TDS to the operator before delivery — and that ₹18,000 should appear in your 26AS just like a cash deduction.

How it lands on the return

For filing, the in-kind prize behaves like any other winning once valued: its FMV is part of your net winnings on the Schedule OS 115BBJ line, and the TDS the operator collected (or you remitted) to release it is your Schedule TDS2 credit, matched to 26AS. The only extra discipline is not forgetting it — because it didn’t arrive as a bank credit, it’s easy to omit, but the operator reported it and it’s likely sitting in your AIS. Report the FMV, claim the TDS, and the prize is handled.

The in-kind rule: a non-cash prize is taxable at FMV (or the operator’s purchase/manufacture price), enters your net winnings, and goes on the 115BBJ Schedule OS line. The operator must ensure the TDS is paid before releasing it — so you may have remitted ~30% upfront, which shows in 26AS and is claimed in Schedule TDS2. The real risk is forgetting the prize, since it never hit your bank.

Filing for a PROGA wind-down: winnings up to August 2025 are still taxable

The post-PROGA situation creates a filing question that trips people up: the app shut down its cash games — do I still report the winnings? The answer is an unambiguous yes, and here is exactly how it works for FY 2025-26.

Why pre-shutdown winnings remain taxable

PROGA banned online money games and the major operators suspended cash play from late August 2025, but the financial year FY 2025-26 runs 1 April 2025 to 31 March 2026. So the cash games ran for roughly the first five months of the year, and every rupee of net winnings you booked in that window is taxable income of FY 2025-26, reportable on the return you file in 2026. The shutdown changed what you can do going forward; it did nothing to the winnings you already earned. A discontinued app is not a discontinued tax obligation — and the operator already reported those winnings to the department, so they’re in your AIS regardless of whether the app still exists.

Wind-down recovery payouts are taxed too

If, after the shutdown, you recovered a stranded balance — banks and intermediaries kept processing withdrawals so users could pull their money out — that recovery payout is also taxed on its net-winnings portion. The operator deducts 30% TDS under Section 194BA on the part of the recovery that represents previously-untaxed net winnings, with no threshold (not even below ₹10,000, since 194BA removed that floor). So a recovery payout that arrived about 30% lighter is TDS, not theft — it’s against your PAN, in your 26AS, and you claim it in Schedule TDS2 exactly like any other gaming TDS. If you’re still fighting to get that stranded balance out, the recovery process and the dispute ladder live on our gaming TDS refund claim and refund dispute recovery pages; once it lands, you file it here.

The filing mechanics are identical

There is no special schedule for wind-down winnings. They go on the same 115BBJ line of Schedule OS, the recovery’s TDS goes in the same Schedule TDS2 under the operator’s TAN, and the whole thing reconciles to the same 26AS/AIS. The only thing PROGA changes about your filing is the timing of when the winnings stopped — for most players, everything sits in Q1–Q2 of FY 2025-26 with the recovery payout possibly in a later quarter. Treat it as a normal gaming return that happens to have a hard stop in August.

The one thing you must not do

Do not deposit again into a discontinued cash game “to unlock” a withdrawal — a new deposit into a money game is now illegal under PROGA, separate from any tax question. And do not skip filing on the theory that “the app is gone so the tax is gone.” The opposite is true: the gone app makes your AIS entry more conspicuous, not less, because there’s no live operator to muddy the department’s record. File the pre-shutdown winnings and the recovery payout cleanly.

The PROGA filing rule: winnings booked before the late-August 2025 shutdown and any wind-down recovery payout are fully taxable in FY 2025-26 and must be filed. They use the same 115BBJ Schedule OS line and Schedule TDS2 as live-app winnings, reconciled to the same 26AS/AIS. The shutdown changes nothing about the tax — it just makes your AIS entry more conspicuous. Never re-deposit to “unlock” a balance; that’s illegal now.

A full worked filing example, end to end

Theory becomes clear on a real figure, so here is one player’s complete year, from winnings to a filed, verified return, using the FY 2025-26 (AY 2026-27) rules.

The player. Vikram, salaried at ₹12,00,000, played fantasy and rummy on two apps before they wound down in late 2025, and recovered a small stranded balance in early 2026. No business income.

App A (fantasy).

• Deposits during the year: ₹50,000 (B)
• Withdrawals: ₹85,000 (A)
• Opening / closing balance: ₹0 / ₹0
• Net winnings (Rule 133) = (85,000 + 0) − (50,000 + 0) = ₹35,000
• TDS deducted by App A at 30% = ₹10,500, shown in 26AS against App A’s TAN, mostly in Q1–Q2.

App B (rummy).

• Deposits: ₹80,000 (B)
• Withdrawals: ₹50,000 (A)
• Opening / closing: ₹0 / ₹0
• Net winnings = (50,000 + 0) − (80,000 + 0) = −₹30,000 → floored to ₹0
• TDS deducted: ₹0. His ₹30,000 real loss is dead for tax.

Wind-down recovery (App A residual). In early 2026, App A returned a small stranded balance of ₹6,000 representing previously-untaxed net winnings of ₹2,000; App A deducted ₹600 TDS on payout, also in 26AS.

His net winnings and tax.

• Total taxable gaming winnings = ₹35,000 (App A) + ₹2,000 (App A residual) + ₹0 (App B) = ₹37,000. App B’s loss reduces nothing.
• Gaming tax under 115BBJ = ₹37,000 × 30% = ₹11,100, + 4% cess = ₹11,544.
• Total gaming TDS in 26AS = ₹10,500 + ₹600 = ₹11,100.
• Top-up owed on the gaming portion = ₹11,544 − ₹11,100 = ₹444 (the cess the 30% TDS didn’t cover), paid as self-assessment tax.

His step-by-step filing (ITR-2, because he has salary and no business income).

1. Gather PAN, Form 26AS (showing App A’s ₹10,500 + ₹600 against its TAN), AIS (showing ₹37,000 of gaming winnings), App A’s Form 16A, and his transaction history. Reconcile: AIS ₹37,000 matches his Rule 133 sum; 26AS ₹11,100 matches the Form 16A. Clean.
2. Pick ITR-2 — salary plus other-source winnings, no business income, so ITR-1 is out and ITR-3 isn’t needed.
3. Salary ₹12,00,000 → Schedule S, taxed at normal slabs with his regime choice and any eligible deductions (which apply to salary only).
4. Gaming winnings ₹37,000 → Schedule OS, Section 115BBJ line, with the quarter-wise split (most in Q1–Q2, the ₹2,000 residual in the later quarter). The utility rejects any negative, so App B’s loss never enters.
5. Gaming TDS ₹11,100 → Schedule TDS2, one row for App A’s TAN totalling the ₹10,500 + ₹600, matched to 26AS.
6. System computes: gaming tax ₹11,544 at 31.2%, minus ₹11,100 credit, leaving a ₹444 gaming top-up. He pays ₹444 via e-Pay Tax as self-assessment tax and enters the challan.
7. Submit, then e-verify via Aadhaar OTP in the same sitting — well inside the 30-day window. The return is now valid and processing.
8. Files by 31 July 2026, avoiding the 234F fee and the AIS-mismatch risk entirely.

What Vikram must not do: net App B’s ₹30,000 loss against App A’s ₹35,000 win (a ₹30,000 under-report, instantly flagged by AIS), file ITR-1, skip filing because “TDS was already deducted,” or forget the ₹2,000 recovery residual (it’s in 26AS and AIS). His real gaming profit across both apps was roughly ₹5,000, but his taxable winnings are ₹37,000 — the no-set-off rule in full.

The end-to-end takeaway: Vikram reports ₹37,000 on the 115BBJ line of Schedule OS (quarter-wise), claims ₹11,100 TDS in Schedule TDS2 under App A’s TAN, pays a ₹444 cess top-up via e-Pay Tax, files ITR-2, and e-verifies via Aadhaar OTP by 31 July 2026. His real profit was ~₹5,000; his taxable winnings ₹37,000 — because App B’s loss has no box, no set-off, no carry-forward.

How the regime choice and your slab interact with gaming tax

A question that comes up the moment a salaried player sees the numbers: does my old-vs-new tax regime choice change the gaming tax, and does my slab matter? The short answer is that the regime and slab govern your other income, while the gaming portion sits in its own walled garden at a flat rate. Getting this clear stops you from making the wrong regime choice for the wrong reason.

The gaming tax is flat and regime-blind

Your net winnings are taxed at a flat 30% under Section 115BBJ regardless of whether you opt for the old regime or the new regime, and regardless of which slab your salary falls into. The special-rate income does not move with the regime knob. So a player in the 5% slab still pays 30% on the gaming winnings, and a player in the 30% slab also pays 30% on the gaming winnings — the gaming rate is the same either way. The regime choice changes how your salary and other normal income is taxed (the slabs, the standard deduction, which Chapter VI-A deductions survive), but it leaves the 115BBJ line untouched.

Why this still affects your overall decision

Even though the regime doesn’t change the gaming tax, it can change your total bill, and that’s where the interaction lives. If you have meaningful 80C / 80D deductions, the old regime might lower your salary tax — but none of those deductions touch the gaming winnings, so the gaming tax is a fixed add-on under either regime. The practical upshot: decide your regime on the merits of your salary and deductions, then add the flat gaming tax on top, the same number in both cases. Don’t switch regimes “to reduce the gaming tax” — you can’t, because the gaming tax doesn’t bend.

The surcharge edge case at high income

There is one place the gaming winnings can quietly push your bill: surcharge. Surcharge applies when your total income exceeds ₹50 lakh, and your gaming winnings are part of total income for that test. So a high earner whose salary alone is near the ₹50 lakh line can be tipped over by gaming winnings, triggering a surcharge on top of the 30% + 4% cess on the gaming portion. For most players this never bites, but if you’re near that threshold, the winnings are not just taxed at 31.2% — they can also be the straw that adds surcharge to the whole picture. Run the numbers (or have a CA run them) if your total income is in that zone.

The regime interaction in one line: gaming winnings are taxed at a flat 30% (+4% cess) under either regime and at any slab — the regime knob never moves the 115BBJ line. Choose your regime on your salary and deductions, then add the fixed gaming tax. The only high-income wrinkle is that winnings count toward the ₹50 lakh surcharge threshold.

The six mistakes that turn a routine gaming return into a notice

Most gaming-tax trouble is self-inflicted and avoidable. These are the recurring filing errors that convert a clean ₹35,000-winnings return into a department notice, each with the one-line fix — gathered here because they map onto the exact steps above.

Mistake 1 — treating “TDS deducted” as “tax done”

The single biggest one. Players see 30% taken at source and conclude the obligation is settled, so they never file. It isn’t settled — the AIS shows winnings against a non-filed return, which is the classic notice trigger, and the credit/refund never materialises. Fix: always file, even when TDS was fully deducted (Step 3).

Mistake 2 — filing ITR-1

A salaried player with gaming winnings who files ITR-1 has filed a defective return, because ITR-1 can’t carry the special 115BBJ rate. Fix: use ITR-2, or ITR-3 with business income (Step 4).

Mistake 3 — netting losses against wins

Players net App B’s loss against App A’s win and report the smaller figure. The AIS shows gross winnings per platform, and the utility bars the negative anyway, so the under-report is flagged immediately. Fix: report each platform’s positive net winnings in full; losses are ignored (Step 5).

Mistake 4 — claiming TDS that isn’t in 26AS

You can claim only what Form 26AS shows. Claiming a higher figure from a Form 16A the operator never filed causes a credit mismatch. Fix: claim the 26AS figure; chase the operator to revise if it’s short (Step 6).

Mistake 5 — a wrong or missing PAN on the gaming account

A mismatched PAN sends the TDS to the wrong 26AS (uncreditable) and can trigger higher-than-30% deduction. Fix: verify the gaming account’s PAN matches your ITR PAN, then get the TDS re-reflected (Step 1).

Mistake 6 — forgetting in-kind prizes or the wind-down residual

A phone, voucher, or a small PROGA recovery payout is taxable but never hit your bank, so it’s easy to omit — yet it’s in your AIS. Fix: report in-kind winnings at FMV and the recovery residual on the same 115BBJ line.

The mistake list, condensed: (1) TDS ≠ filed — always file; (2) never ITR-1; (3) never net losses against wins; (4) claim only 26AS TDS; (5) keep PAN correct on the gaming account; (6) don’t forget in-kind prizes or the wind-down residual. Five of the six are about reconciling to the department’s data before you submit.

Quick-reference filing checklist

Print this. Each line is a step from the page above, in order.

For the case where you’re still chasing a stranded balance before any of this, start at gaming TDS refund claim. For what the operator was allowed to deduct from your payout in the first place — minimums, charges, and the 30% cut — see minimum withdrawal and charges. For a withdrawal that never arrived, the full escalation ladder is on 3 Patti withdrawal. And if the operator simply won’t pay an owed, clean balance, the dispute path is refund dispute recovery.

Frequently asked questions

1. How do I file ITR for online gaming income in 2026?

Use ITR-2 (or ITR-3 if you have business income), report net winnings on the Section 115BBJ line of Schedule OS with the quarter-wise split, claim the 30% TDS in Schedule TDS2 using each operator’s TAN matched to Form 26AS, pay any small cess top-up, then submit and e-verify within 30 days — filing by 31 July 2026 for FY 2025-26. You cannot use ITR-1.

2. Which ITR form is correct for gaming winnings — ITR-1, ITR-2 or ITR-3?

Never ITR-1. It cannot carry income taxed at the special 115BBJ rate, so a gaming player who files it has filed a defective return. Use ITR-2 if you’re salaried, a pensioner, or have capital gains with no business income, and ITR-3 if you have business or professional income. The size of the winnings is irrelevant — the special rate, not the amount, rules out ITR-1.

3. Where exactly do online gaming winnings go in the ITR?

On the dedicated Section 115BBJ line of Schedule OS (Income from Other Sources), entered as net winnings with a quarter-wise break-up that sums to the annual figure. This is separate from the Section 115BB line used for traditional lottery and game-show winnings. Don’t use the generic “other income” box — the 115BBJ line is what applies the flat 30% instead of your slab rate.

4. How do I claim the 30% TDS the gaming app deducted?

Enter it in Schedule TDS2 (TDS other than salary): the operator’s TAN, the gross amount, and the TDS deducted, matched to Form 26AS — one row per operator. This converts the 30% already taken into a credit against your final tax. You can claim only the figure that appears in 26AS, so verify each line against the operator’s Form 16A before submitting.

5. Where does the data for my gaming ITR come from?

From three official statements behind your e-filing login: Form 26AS (the 194BA TDS, with each operator’s TAN, by quarter), the AIS (your reported winnings), and the TIS (the summarised winnings total). Anchor all three to each operator’s Form 16A. You file from these, not from the app’s screen — and they must reconcile, because the department validates your return against them.

6. Do I have to file if the app already deducted TDS?

Yes. TDS is an advance, not the final tax. Filing is the only way the 30% gets credited and any over-deduction comes back as a refund. Beyond that, gaming winnings get no basic-exemption shelter, and Rule 12BA makes filing mandatory once your aggregate TDS/TCS exceeds ₹25,000 — which gaming TDS alone breaches at roughly ₹83,000 of net winnings.

7. What is the deadline to file my gaming ITR for FY 2025-26?

The original due date is 31 July 2026 for individuals not requiring audit. A belated return under Section 139(4) can be filed until 31 December 2026, but with a Section 234F late fee (₹5,000, or ₹1,000 if total income is below ₹5 lakh) plus 234A interest on unpaid tax. For gaming income, filing late also leaves a visible AIS mismatch the department is actively pursuing.

8. How are “net winnings” calculated for the form?

Per Rule 133, net winnings = (withdrawals + closing balance) − (your deposits + opening balance) for each platform across the financial year, floored at zero. On a ₹40,000-deposit, ₹70,000-withdrawal, ₹5,000-closing year, that’s ₹35,000. Compute it per platform and total the positive figures; the form bars negatives, so losing platforms contribute zero.

9. Can I set off my loss on one app against my win on another in the ITR?

No. The ITR utility rejects negative figures in the online-gaming field, so a ₹40,000 loss on App B cannot reduce a ₹50,000 win on App A — you report and pay 30% on the full ₹50,000. There is no set-off across platforms or against other income, and no carry-forward. Your taxable winnings can legitimately exceed your real net profit.

10. Will I get a refund of the gaming TDS?

Usually no for a straightforward net winner — the 30% TDS is slightly less than the 31.2% final tax, so you typically owe a small cess top-up of a few hundred rupees. A refund arises only when TDS was over-deducted (gross or duplicate reporting later corrected), you suffered higher-rate deduction from a missing PAN, or you have excess credits elsewhere — and only if you file to claim it. The refund mechanics are detailed on our gaming TDS refund claim page.

11. What happens if I don’t e-verify my return?

A submitted return that is not e-verified within 30 days is treated as not filed — invalid, as if you never submitted it. No tax credit, no refund, and if the 30 days lapse past the deadline you’ve effectively missed it. E-verify immediately after submitting, ideally via Aadhaar OTP, which takes seconds and starts processing.

12. I won a phone (not cash) in a tournament — do I report it?

Yes. In-kind winnings are taxable at fair market value (or the operator’s purchase price if it bought the prize, or the price it charges customers if it manufactured it). A ₹60,000 phone is ₹60,000 of winnings on your 115BBJ Schedule OS line, carrying roughly ₹18,000 of TDS the operator had to ensure was paid before releasing the prize. Because it never hit your bank, the real risk is forgetting it — but it’s in your AIS.

13. My app shut down under PROGA — are my winnings still taxable?

Yes. FY 2025-26 runs 1 April 2025 to 31 March 2026, and the cash games ran until the late-August 2025 shutdown, so winnings booked in those first five months are fully taxable and must be filed. Any wind-down recovery payout of a stranded balance is taxed too — 30% TDS under Section 194BA, no threshold. They use the same 115BBJ Schedule OS line and Schedule TDS2 as live-app winnings.

14. The TDS in my 26AS is less than what the app told me it deducted — what do I do?

You can claim only the TDS that appears in Form 26AS, so do not claim the higher Form 16A figure — that causes a credit mismatch. Chase the operator to file or revise its TDS return so the missing amount appears in 26AS, then claim it. If it can’t be fixed before the deadline, file with the credit you can prove (the 26AS figure) and revise the return later, before 31 December 2026.

15. My gaming account had the wrong PAN — can I still claim the TDS?

Only after fixing it. TDS deducted against a wrong or old PAN lands in someone else’s 26AS (or yours under a different number) and cannot be claimed on your return. Correct the PAN with the operator, get the TDS re-reflected against your correct PAN in 26AS, then claim it in Schedule TDS2. A missing PAN can also have caused higher-than-30% deduction, recoverable only by filing — another reason to fix it and file.

16. Is this page tax advice?

No. This is a sourced filing walkthrough, not tax advice, and it is not written by a tax professional. Every form, schedule, section and deadline is tied to the Income-tax Act, CBDT notifications, the e-filing portal, or a named tax source. For a filing decision that affects your money, consult a qualified chartered accountant.

Sources & method. The forms, schedules, sections and deadlines on this page are built from primary and authoritative sources, not personal filing tests. Key references: the income-tax e-filing portal for ITR/AIS/TIS/26AS and e-verification; Section 115BBJ, Section 194BA, Rule 133, Rule 12BA, and CBDT Circular No. 5/2023 (22 May 2023) for the rate, net-winnings formula, in-kind valuation and filing trigger (Income Tax India; PKC Management Consulting; TheTaxTalk); G2G News on Schedule OS/TDS2 reporting and ITR-2/ITR-3 selection; ClearTax on viewing Form 26AS; and CAalley on the Rule 12BA filing trigger and non-filer enforcement. The full law explainer is our online gaming tax India 2026 page, with the section-renumbering detail in TDS on online gaming. This page is information, not legal or financial advice — verify each step against the live e-filing utility and a qualified CA before you file.