Recording requirements

What a session needs to pass review and get paid.

The short version
Do this Do not do this Frame rate troubleshooting What's captured If a clip is not approved

Do this

A session missing any of these can not be paid.

Record at 1080p or better
Hold 60 fps
Within 5% of 60, for at least one unbroken 10 minute stretch.
Play fullscreen
Set the game language to English
Menus, subtitles and cutscenes all in English. Change it in the game settings before you start recording.
Turn on Do Not Disturb
Windows and N on Windows 11, Focus assist on Windows 10.
Show your key bindings
Start the recording, open Options > Controls and scroll through all of them. Custom binds are fine.
Use mouse and keyboard
Play 30 minutes or more in one go, longer is better
Play normally
Cutscenes, menus, map and inventory all count as paid. A higher level character and mixed content are more useful than an hour of the same thing.
Let uploads finish with the recorder open
Closing it early leaves a half uploaded session we can not review. If it is stuck for hours, hit Report a problem and message us.

Do not do this

The first three fail the session. The rest come off your hours.

Do not use macros, bots or auto clickers
This ends the working relationship, not just the session.
Do not edit or convert the file
Do not send a session twice
Do not run overlays
The in game fps counter, Discord and Steam overlays, and other recording software. We need a clean view of the game.
Do not leave it recording while you are away
Stop it and start a new session when you are back. Idle time comes off your hours.
Do not alt tab
Any second with another window in front of the game is removed.
Do not type in the in game chat
The time you spend typing, and a little around it, may not count toward your hours.

Frame rate troubleshooting

The most common reason a session does not pay.

What 60 fps means here

The recorder always writes a 60 fps file. That is not the same as your game drawing 60 new pictures a second. If your game runs at 42, your screen shows some pictures twice, and the file holds 42 real frames plus 18 copies.

We count the real ones. Copies provide no new information, so they do not get paid. That is why a session can look normal to you and come back short on hours.

To be payable, a session has to run 30 minutes or more and hold within 5% of 60 fps for at least one unbroken 10 minute stretch inside it.

How to check your fps

Do this in a short test clip, then turn the counter off and record.

  • In the game. Turn on its FPS counter. Diablo IV: Options > Gameplay, Show FPS (Ctrl and R on most builds). League of Legends: Ctrl and F. World of Warcraft: Ctrl and R.
  • Windows Game Bar. Press Windows and G, open the Performance widget.
  • Your driver software. The NVIDIA app overlay, or AMD Adrenalin with Ctrl, Shift and O.

Check it in a hard fight, not in town. A big pack of monsters, a Helltide, a boss with the screen full of effects. If it holds 60 in a fight it'll hold 60 anywhere.

How to raise your fps

Work down the list and check again after each one. Most people find 60 in the first few.

  • Set the game to fullscreen. Options > Graphics > Display Mode.
  • Drop your resolution before you drop 60. 1080p at a steady 60 beats 1440p at 45.
  • Lower the graphics preset to medium or low. Shadow quality, anti aliasing, SSAO and fog give back the most.
  • Turn ray tracing off if your card has it.
  • Leave the frame rate uncapped. Check Options > Graphics for a low max fps setting or a VSync lock and clear it.
  • Close everything else. Browser tabs, Discord, streaming software, and other recorders like ShadowPlay or Game Bar capture.
  • Point Windows at your real graphics card. Settings > System > Display > Graphics, find your game, set it to high performance. Laptops often use the built in chip instead.
  • Set power mode to best performance in Settings > System > Power, and plug a laptop in. Battery mode cuts frame rates hard.
  • Update your graphics driver from NVIDIA, AMD or Intel directly.

Still under 60 after all of that? Message us with your user number and what you are seeing.

What's captured

  • Game audio only. Nothing else from your computer, and never your microphone.
  • Every key and mouse move, across the whole computer, not only inside the game.
  • The titles of windows you have open while the recorder is running.

Do not type passwords while it is running, and do not open anything you would not want recorded.

Party play and voice chat

Playing with other people on the program is fine, and so is in game voice chat when everyone in the party is on the program. Each player is reviewed on their own recording.

If a clip is not approved

The note on your home page says which check it missed.

Your game was not holding 60fps while recording
Your machine was drawing under 60 for most of the session. Work through the troubleshooting above. Lowering the resolution is usually the fastest fix.
Recording did not hold steady 60fps
Frames were dropped or the recording stalled, even if the game felt fine. Usually heavy background software. Close other recorders and try again.
Video is below 1080p
Raise the resolution in Windows display settings and in the game.
Recording too short or the file was cut
Under the minimum, or the recorder or PC was closed before the session finished writing.
Recording must capture the game in fullscreen
The game wasn't in front for enough of the session.
Recording timing issue, the capture could not keep up
The video and your key presses drifted apart. Make sure the recorder is up to date, then tell us your graphics card. This one is often on our end.
Video and input log do not match
The video was edited, converted or swapped. Upload the raw recorder output.
Input log missing or unreadable
Upload the whole recorder output, not the video on its own.
Duplicate of an earlier submission
This session, or a long stretch of it, has already been sent in.
Under review
Not a rejection. Somebody is looking at it.
Idle time was not counted
Not a rejection. The session was approved with the idle time taken off.

If the note does not match what you saw, message us with your user number and the date and time of the session.