How to get paid to test apps and games
What testing really pays, the four ways testers earn, the profile that gets you selected, and the red flags that mark a scam before you waste a month.
The honest money picture
Most useful thing first: the popular idea of paid app testing is inflated. You will not earn a full-time salary tapping through apps in your spare time. What genuinely exists is a range of small, real payments for structured work, plus a route into QA employment for people who want it.
There are two distinct economies, and mixing them up is where people get disappointed:
- Public betas for apps and games. Almost never cash. You get early access and sometimes store credit, an in-game reward, or a free subscription.
- Research and testing platforms. Real money, per test or per session, for people who match a study's requirements, and paid work is regularly available if your profile matches a demand.
So the realistic plan is not “get paid to beta test games”. It is: use public betas to learn the craft and build a record, and use research platforms and specialist QA work to earn. Both halves are in this guide.
The four ways testers get paid
1. Unmoderated usability tests
You are given a device, tasks and a time limit. You record your screen and speak your thoughts aloud. Nobody watches live. Payment is per completed test. This is the easiest paid work to get, needs no scheduling, and is the best place to start: the only real skill is talking while you use an app, which takes one or two tries to get comfortable with.
2. Moderated research sessions
A researcher interviews you on a video call, usually 30 to 60 minutes, while you share your screen and work through tasks. Better paid than unmoderated work, harder to get, and it rewards people who can say what they are thinking without being prompted. A quiet room, working microphone and reliable connection are the entry requirements.
3. Per-issue bug work and bounties
Some programmes pay for confirmed defects, sometimes at a fixed rate, sometimes through a structured bounty scheme. The report must be reproducible and follow the required format exactly. This is the most variable income of the four and the least suitable as a plan; treat it as upside on top of a session or two.
4. Contract QA and game testing
Studios and QA firms hire short-term testers around a release, often for a defined cycle, sometimes on-site and sometimes remote. This is employment rather than a side task, and it is what a year of good reports plus a portfolio can lead to. It is also the route most people actually want without knowing it: steady, paid, and it uses exactly the skills described in the rest of this guide.
What the rates look like
Figures below are typical ranges for individuals doing this in their own time. They move with region, currency and demand, so treat them as a shape rather than a promise.
| Work | Typical payment | Notes |
|---|---|---|
| Unmoderated test | Small fixed fee per test | 10–20 minutes of work. Volume matters more than rate. |
| Moderated session | Several times the unmoderated fee | 45–60 minutes plus setup. Often the best hourly rate available to a beginner. |
| Diary study | Paid over several days | Frequent short entries across a week or two. Rewards reliability. |
| Confirmed bug (bounty) | Per accepted issue | Highly variable; strong reports only. |
| Public game or app beta | Access, credit or a small gift card | Not income. Genuinely useful as a portfolio. |
The uncomfortable arithmetic. One test a week is pocket money. Ten tests a week is not achievable for most people, because studies are matched to profiles and demand is uneven. Plan for a side income you build slowly, or aim at contract QA where the pay is structured.
Set up a profile that gets picked
Testing platforms select on fit, not enthusiasm. Your profile is a matching document: the closer it is to the truth, the more often you get chosen for studies you can actually complete.
- Devices, exactly. Model, OS version, and whether you have a tablet, a desktop or a console. Studios regularly need old devices and unusual screen sizes.
- Demographics, accurately. Age band, region, household and work situation are often the whole reason a study exists. Answer them truthfully; a mismatch shows up immediately and hurts your standing.
- Interests and habits. Banking, health, shopping, fitness, gaming, travel, parenting. Studies recruit by behaviour, so list what you actually do.
- Accessibility needs and languages. Both are in constant demand and both are paid.
- Availability. Real slots, in your own time zone. Agreeing to a session you cannot attend is the fastest way to lose access.
- Setup notes. A quiet room, wired or stable internet, headphones with a microphone, and a computer that can screen-record without stuttering.
Join three or four platforms rather than one, fill each profile once, and keep notifications on. Selection is a numbers game and the studies go to whoever responds first.
Your first paid test
Here is what a first unmoderated test actually involves, so nothing surprises you.
- The screener. A short questionnaire decides whether you fit. Answer fast and honestly; talk your way into a study you do not match and you are removed, and the platform records it.
- The brief. Usually a page: what to do, how long, what to say aloud. Read it before you start recording. Half of poor tests are people who skipped the brief.
- The recording. Share your screen, unmute, and narrate. “I am looking for the settings… I would expect it under my profile… that is not where I thought” is exactly the data they want. Silence is wasted test time.
- The tasks. Complete them in order. If you get genuinely stuck, say so and move on; do not spend twelve minutes hunting for a button. Being stuck is a finding, not a failure.
- The wrap-up questions. Short, written or spoken. Answer specifically: name the screen and the moment, not “it was fine”.
- Submission. Upload, check it processed, and keep the confirmation. Payments usually release a few days after the client accepts the recording.
Do two or three of these and you will have both a payment and a track record that makes the next application easier.
Red flags: how to spot a scam
Any offer that inverts the money flow is a scam. Testing work pays you; it never requires you to pay first. Beyond that, these are the patterns to walk away from.
- You must pay to join, or buy a “tester kit” or training pack. No legitimate programme sells access to testing work.
- You are asked to deposit money to “unlock” tasks or withdrawals. This is the most common version of the fraud. There is no account to fund.
- Bank details, card numbers or a copy of your ID before any contract. A real platform pays into a payout account you control, set up inside its own dashboard. It does not need your card number.
- Paid work that is only messaging and liking things. That is not testing; it is a task scam with a testing story attached.
- Recruitment only through a chat app, with no company name or website. Look the company up independently, and check the domain's age.
- Urgency and secrecy. “Only three slots, do not tell anyone, install this file now.” Beta builds arrive through TestFlight or a store testing track, not as an attachment from a stranger.
- A guaranteed income figure. Nobody can guarantee study selection, because selection is matched to a client's requirements.
One rule covers almost everything. If getting paid requires you to pay, install something from a link, or hand over card details, stop. A real programme asks for a device and your time, and nothing else.
How to grow from one-off to regular
The transition from occasional tests to reliable work is made of unglamorous things.
- Never miss a booked session. Reliability is scarce. Two researchers who trust you will invite you back before a hundred strangers will.
- Keep a personal report log. A simple list of every issue you have filed, with the app name stripped out. It becomes your portfolio when a studio asks what you have tested.
- Specialise. Accessibility, payments and checkout, games, health apps, or a non-English market. Specialists get requested by name; generalists wait for the queue.
- Learn the vocabulary. Regression, reproduction steps, severity versus priority, crash log, device matrix. Using the words correctly in a report signals experience even before you have any.
- Ask for the next thing. At the end of a contract, one short message saying what you tested and that you are available for the next cycle is how most testers get their second engagement.
Payouts, records and tax
Three practical points that people learn late.
- Check the payout method before you invest time. Some platforms pay only by a specific transfer service or gift card, and a balance you cannot withdraw is not income.
- Keep your own record. A simple sheet: date, platform, study or issue, amount, whether it was paid. It takes a minute and saves an afternoon at tax time.
- Assume it is taxable income where you live, including small amounts and gift cards in many jurisdictions. Rules vary by country, so check your own; it is not advice we can give for your situation.
And a fourth, less practical point: the testers who earn steadily are rarely the ones who found the cleverest platform. They are the ones who answered promptly, showed up, and wrote reports people could act on for six months without a gap. That is a boring answer, and it is the true one.
Next: how to become a beta tester, and what beta testing actually means.
Found a programme that looks too good, or a payment that never arrived? Tell us about it and we will tell you plainly what we think.