The recording could not be started EN

The usual causes, in the order worth checking, and how to report it if none apply.

If a recording doesn't start, you'll usually see "The recording could not be started" in the extension - or nothing seems to happen at all after you click Start. Work through these causes in order; most take only a few seconds to check.

Check these, in order

When you record a window, a screen, or a tab other than the one you clicked Start from, Chrome shows its own "Choose what to share" dialog before Rekorder can start capturing. If you click Cancel, close that dialog without picking anything, or Chrome doesn't show it at all, the recording never starts - and there's no error message either. The popup or control bar just returns to its starting state.

Click Start again and pick a source in the dialog this time.

2. A performance check is running

Rekorder occasionally runs a short benchmark in the background to check what your device can handle. While it runs, the Start button in the popup turns grey and shows a spinner instead of "Start". Wait a few seconds for it to finish, then click Start again.

3. Camera or microphone access

If your recording settings include a camera or a microphone, Chrome needs to grant Rekorder access to them at the moment you start:

If access was denied, see Camera or microphone permission is blocked.
If the device can't be used for another reason (missing, in use elsewhere, disconnected), see "Camera or microphone unavailable".

4. You're at a free plan limit

If your account has reached its 60-minute or 1 GB free limit, Rekorder tells you which limit you've hit and offers to delete a recording or upgrade, rather than starting. See What happens when you go over your free limits.

5. You were signed out

If your session ended, the extension shows a sign-in screen instead of starting. Sign in again and retry. See The extension shows a login screen when you were signed in.

If none of this explains it

If you've checked the above and the recording still won't start, report it so support can see what happened:

Logging off: the error window offers a Send button - click it to report just this failure.
Logging on: the report already went out automatically; there's nothing else to do.
Offline mode: nothing is sent automatically. Turn on Logging, repeat the problem, then download and send the saved log.

See How do I report a bug from inside the app? and Turn on logging and send a log file to support for the full steps.