Real Pay · Website and app feedback tests
Is UserTesting worth it? Its real pay, after the fees nobody lists
Partial — your numbersPARTIAL — this page runs on your numbers
UserTesting publishes a pay model, never what you net per total hour in your city — and no truthful per-city dataset exists. This checker takes your logged numbers; any national band shown is labeled with its source and is a sanity rail, never a promise.
UserTesting pays real money for spoken opinions, at published per-test rates — and the honest catch is the funnel before the test: screeners you fail pay nothing. PARTIAL because your qualification rate is yours alone. Log the screeners; everyone else forgets them, which is why everyone else's hourly is fiction.
The part the poster skips: Ten screeners at three minutes each is half an hour of unpaid auditions per paid test. The people who rate UserTesting highly are the people whose profiles match many tests — it is a fit question before it is a pay question.
What UserTesting asks of you
The requirements
- Car: no car needed
- Published startup cost: $0
- Body: any level
- Place: from home
Week one, in short
Day 1: complete your profile in full and take the practice test seriously — it gates everything.
The full first-week plan — day blocks, the shape of the week, and the quit signal — is in the Fit & Real Pay Pack.
The fee schedule, in the open
| Fee / rule | What it is | Source |
|---|---|---|
| Published per-test pay | Short tests from about $4; standard ~20-minute tests about $10; live conversation sessions $30–$120 by length | UserTesting contributor pages |
| Why this page is PARTIAL | Per-test pay is published, but how many tests you qualify for is not — screener rejections are unpaid and vary by your profile. The engine runs on your completed tests and your screener time. | FitSideHustle method |
Fee schedule: UserTesting's published contributor pay ranges — checked October 23, 2026.
Not run the Fit Finder yet? A fee table can't tell you whether this fits your calendar, your car, or your handbook. Run the Fit Finder first →