Back to Blog

Google Play Withholding Tax in 2026: A Step-by-Step Guide to W-8BEN, Country Rates, and Treaty Relief

Google Play Withholding Tax in 2026: A Step-by-Step Guide to W-8BEN, Country Rates, and Treaty Relief

If you sell apps, subscriptions or in-app products on Google Play from outside the United States, a slice of your earnings can be withheld before it ever reaches your bank account. The reason is withholding tax (WHT): in several markets, local law requires Google or its payment processor partners to deduct tax on the developer proceeds generated by customers in that country. Google publishes the current rules on its Withholding tax (WHT) help page, and the list is longer than most developers expect — Brazil, Egypt, India, Kenya, Kuwait, Myanmar, Sri Lanka, Taiwan and Tanzania all appear on it. This step-by-step guide explains how WHT works, the rates that apply, how the W-8BEN form and double tax treaties change the number, and how to verify your own setup before a deduction shows up as an unexplained shortfall.

The one-line version: withholding tax is deducted from your Google Play earnings by Google in certain countries, so it lowers the amount you are paid, not only the amount you settle after filing. Google states plainly that it cannot provide tax advice, so confirm your position with a qualified advisor.

1. How withholding tax on Google Play works

Google's WHT page describes a straightforward mechanism: developers offering Google Play app and in-app purchases made in certain countries may have withholding taxes deducted from their earnings, because of requirements in those local markets. Google says it monitors tax-regulation changes and notifies developers of changes to its tax rules. The deduction is made by Google or its payment processor partners and is often tied to how customers pay. For direct carrier billing (DCB) purchases in countries such as Egypt, Kuwait, Myanmar and Sri Lanka, the withholding attaches to that payment method. For others — Taiwan, for example — Google takes full responsibility for the WHT on paid Google Play transactions, so you are not obligated to calculate or remit it separately. The practical point is the same either way: the number you see in your payments statement is already net of it.

2. The country list and the rates that apply today

These are the markets Google currently documents, with the rate attached to each. Check the Withholding tax (WHT) page before you rely on any of them, because local rates change.

3. W-8BEN vs W-9: which form your account needs

Before any of this, your payments profile has to carry the right IRS form. Google's Enter merchant tax information page is explicit: US-based merchants must submit the IRS W-9, while everyone else must submit the Certificate of Foreign Status (W-8BEN) to the IRS. Individuals and sole proprietors using a Social Security Number must enter it exactly as it appears in IRS records; corporations, partnerships and LLCs must provide the federal Employer Identification Number (EIN) and their exact legal business name. Google warns that you have a limited number of attempts to provide the correct information — so copy the name and number from the source document rather than typing them from memory.

4. How a tax treaty lowers the rate

A treaty rate is not a separate form you file with Google; it is a determination Google makes from the tax information you provide. Where a supported country has a double tax treaty with the market applying the withholding, and you have supplied your tax information, Google determines whether you qualify for the treaty rate. The Brazil guidance shows the shape of it: with a valid treaty and the right tax information, a reduced rate on IRRF may apply. The UAE note shows the other half — an affected developer may reduce IRRF to the normal rate by uploading a copy of a tax residency certificate. The takeaway is to keep a current tax residency certificate on hand: a treaty benefit you cannot document is a benefit you do not get.

5. Enter or update your tax information, step by step

Google's own instructions, condensed:

  1. Sign in to Play Console.
  2. Go to Settings → Payments settings, and under "Payments profile" find "[your country] tax info".
  3. Click Edit, then Add tax info or Update tax info.
  4. Answer the questions and submit the W-9 or W-8BEN from within the profile, then click Save.
  5. For country-specific blocks, scroll to the matching section — for example "India tax info" for your PAN, "Kenya tax info" for your PIN, "Tanzania tax info" for your TIN, or "Taiwan withholding tax info" — and update it the same way.

6. The tax forms and certificates you receive

Google files Form 1099-K for Google Play developers who make more than US$20,000 in gross sales and have more than 200 payment transactions a year; accounts based in Massachusetts or Vermont receive one from US$600 in gross volume. If you receive a 1099-K you did not expect, the usual cause is two accounts sharing one tax identification number whose combined volume crosses the threshold. One caveat to plan around: when Google applies the Taiwan WHT, it states that it cannot provide a WHT certificate issued by the Taiwanese tax authorities in your name, so keep your own records. Year-end tax forms can be requested, revised or voided through Google's year-end tax form request, with blackout dates around each year-end.

7. The neighbouring settings: VAT and product classification

WHT sits next to two other tax switches you set per product. Under Tax and compliance settings, any app distributed in the EEA must be classified as Digital Content or Service — the choice changes the EEA right of withdrawal — and sellers of digital news, books, video, music or audio may select reduced VAT rates in eligible countries. Google's Tax rates and VAT page lists the many countries that require tax-inclusive pricing. These are separate from WHT, but they share the same principle: the amount a customer pays and the amount you are paid both depend on settings you are responsible for getting right.

8. A preflight check before you scale

Six checks, in order. One: confirm your payments profile carries the correct form (W-9 or W-8BEN) and that the name and TIN match your IRS or local records exactly. Two: enter the country-specific identifiers — India PAN, Kenya PIN, Tanzania TIN, Taiwan VAT ID or exemption — wherever they apply. Three: keep a current tax residency certificate if you claim, or intend to claim, a treaty rate. Four: model your take-home against the country list above so a 5% or 20% deduction is expected, not a surprise. Five: reconcile what you are paid against the deduction rules for the countries your customers buy from. Six: take anything material to a qualified tax advisor — Google's page states it cannot give tax advice, and this article is general information, not advice. Run before a payout cycle, these checks turn a vague worry about "missing money" into a line you can explain.

Sources

Running developer accounts at scale? We handle the operational side.

Click to choose a file · right-click → Paste, or press Ctrl/⌘+V to paste a screenshot

You can also drag a file onto this box.

We reply to the email you provide. Your details stay with KappS.

✔ Submitted

We received your message and will reply within 24 hours.

Or email expert@kapps.store
← Back to edit