Record Android Screen with ADB (No Root)

11 min read Learn how to capture high‑quality screen recordings on any Android device using ADB without rooting. Detailed steps, options, and troubleshooting included. October 05, 2026 05:30 How to Record Android Screen Using ADB (No Root) – Step‑by‑Step Guide

Many Android users need a reliable way to capture what’s happening on their device – whether it’s a bug demo, a tutorial, or a game highlight. The built‑in screen recorder that ships with recent Android versions is convenient, but it often lacks fine‑grained control over bitrate, resolution, or duration. Using adb (Android Debug Bridge) you can record the screen from a computer, adjust technical parameters, and avoid any need for root access.

What you’ll get: A .mp4 video saved on your computer that matches the settings you chose, without installing any extra apps on the phone.

Before You Start

  • Computer with ADB installed – Windows, macOS, or Linux. If you haven’t installed the platform‑tools package yet, download it from the official Android developer site and extract it to a folder you can access.
  • USB cable – Use a data‑capable cable; charging‑only cables won’t allow ADB communication.
  • Device with USB debugging enabled – Settings > About phone > tap Build number seven times, then go to Settings > System > Developer options > enable USB debugging.
  • Enough free storage on the device (for the temporary recording) and on the computer (for the final file).
  • Battery level – Aim for at least 50 % or keep the phone plugged in; screen recording can be power‑intensive.

Step 1 – Verify ADB Connection

  1. Open a terminal (Command Prompt on Windows, Terminal on macOS/Linux) and navigate to the folder containing adb.
  2. Run adb devices. You should see your device’s serial number followed by device.
    adb devices
    List of devices attached
    ABC123456789    device
  3. If the device shows as unauthorized, unlock the phone and tap Allow USB debugging on the prompt.
If no device appears, double‑check the cable, enable USB debugging, and make sure the proper USB mode (usually “File Transfer” or “PTP”) is selected.

Step 2 – Choose Recording Parameters

The screenrecord command supports several optional flags. Understanding them helps you avoid common pitfalls such as low‑quality video or premature termination.

  • --size WIDTHxHEIGHT – Sets the output resolution. If omitted, the device records at its native resolution.
  • --bit-rate BITRATE – Bitrate in bits per second (default 4 Mbps). Higher bitrate improves quality but creates larger files.
  • --time-limit SECONDS – Maximum duration (default 180 seconds). Android caps recordings at 180 seconds unless you use the --time-limit flag (max 1800 seconds on most devices).
  • --rotate – Rotates the video 90° clockwise; useful for portrait‑only apps on a landscape‑oriented device.

Example choice for a 1080p, 8 Mbps, 2‑minute capture:

--size 1920x1080 --bit-rate 8000000 --time-limit 120

Step 3 – Start the Recording

  1. Run the screenrecord command via ADB shell. The command writes the video file to the device’s /sdcard/ directory.
    adb shell screenrecord /sdcard/record.mp4
    This starts an indefinite recording (up to the default 180 seconds). To apply custom parameters, include them after screenrecord:
    adb shell screenrecord \
      --size 1920x1080 \
      --bit-rate 8000000 \
      --time-limit 120 \
      /sdcard/record.mp4
  2. As soon as you press Enter, the device begins capturing. You’ll see a small red dot in the status bar indicating an active recording.
  3. When you’re ready to stop, press Ctrl + C** in the terminal. The command terminates and the file is finalized.
If you need to start the recording without keeping the terminal open, you can launch it in the background:
adb shell "screenrecord /sdcard/record.mp4 &"
Later, stop it with adb shell pkill -l2 screenrecord.

Step 4 – Retrieve the Video File

  1. Pull the file to your computer:
    adb pull /sdcard/record.mp4 ./record.mp4
    The file will appear in the current directory.
  2. If you prefer to keep the video on the device, you can view it directly with the Gallery app or any video player.

Step 5 – Verify the Result

Open the record.mp4 file with your favorite media player (VLC, MPV, etc.). Check for:

  • Correct resolution and orientation.
  • No dropped frames or visual artifacts.
  • Audio (if you recorded a game or app that outputs sound). Note: screenrecord captures internal audio only on Android 10+; on older versions you’ll get silent video.
If the video is silent on Android 9 or earlier, you’ll need a separate method (e.g., an external recorder or a third‑party app) because ADB cannot capture system audio on those versions.

Alternative: Using Built‑In Screen Recorder

Most Android 11+ devices ship with a native screen recorder accessed from the Quick Settings panel. The built‑in tool is convenient but lacks the ability to set bitrate or resolution, and it may embed a watermark on some OEM skins. The ADB method described above gives you full control and produces a clean, share‑ready file.

Troubleshooting Common Issues

1. "screenrecord: command not found"

This error means the device’s screenrecord binary is missing – typically on very old Android versions (< 4.4) or custom ROMs that stripped it. In that case, consider using a third‑party screen‑recording app from the Play Store.

2. Recording stops early (e.g., after 30 seconds)

Possible causes:

  • Insufficient storage – The device runs out of space in /sdcard/. Free up space or record to a different folder on an external SD card (if available): adb shell screenrecord /storage/XXXX-XXXX/record.mp4.
  • Battery saver – Some manufacturers halt background tasks when battery saver is active. Disable battery saver during recording.

3. Video is black or shows only a static frame

Often caused by a locked screen. Make sure the device stays awake:

  1. Enable Stay awake while charging in Settings > Developer options.
  2. Or use adb shell settings put system stay_on_while_plugged_in 1 before starting the capture.

4. Audio is missing on Android 10+

If you see no audio despite the OS supporting internal capture, check the following:

  • The app you’re recording must be playing audio through the device’s main output (not Bluetooth headphones).
  • Some OEM skins disable internal audio capture for privacy. In that case, you may need to route audio via a Bluetooth headset and record externally.

5. "Permission denied" when pulling the file

This can happen if the device is running Android 11+ with scoped storage restrictions. Use the run-as trick or copy the file to a public directory first:

adb shell cp /sdcard/record.mp4 /storage/emulated/0/Download/record.mp4
Then pull from the Download folder.

Advanced Tips

  • Record to a specific frame rate: Android’s screenrecord does not expose a direct frame‑rate flag, but you can approximate it by adjusting --bit-rate and resolution. Higher bitrate yields smoother motion.
  • Combine with logcat: For debugging UI glitches, start a parallel adb logcat capture and sync timestamps later.
    adb logcat -v time > log.txt &
    adb shell screenrecord /sdcard/record.mp4
  • Automate with a script: Create a simple batch or shell script that accepts duration and filename arguments, then runs the full workflow (start, wait, pull, clean up).

Safety and Data‑Loss Considerations

Recording writes a temporary file to the device’s internal storage. Deleting the file before pulling it will lose the video. Always verify the file exists (adb shell ls /sdcard/record.mp4) before pulling.

While the process is safe for the OS, keep the following in mind:

  • Long recordings (over 10 minutes) can consume several hundred megabytes – ensure you have enough free space.
  • Running screenrecord while the device is under heavy load (e.g., gaming) may affect performance slightly.

Wrap‑Up

Using ADB’s screenrecord tool gives you a lightweight, root‑free way to capture exactly what you need on any Android device. By controlling bitrate, resolution, and duration, you can produce professional‑grade recordings without third‑party apps, and you retain full command over where the file ends up. If you encounter any of the issues covered in the troubleshooting section, follow the suggested fixes, and you’ll have a reliable screen‑recording workflow for tutorials, bug reports, or personal archives.

User Comments (0)

Add Comment
We'll never share your email with anyone else.