How to Record Your Screen on elementary OS
Screen recording is useful for creating tutorials, reporting bugs, demonstrating an application, or saving a short explanation for someone else. On elementary OS, you can capture the entire desktop with a built-in utility or install a dedicated recorder when you need advanced controls.
The best choice depends on the type of video you want to make. A quick demonstration may require only a few clicks, while a polished tutorial could need microphone mixing, webcam overlays, scene layouts, or separate audio tracks. elementary OS supports both approaches through its native Screenshot utility and several Linux-compatible applications.
Before recording, close private notifications, check the available storage, and decide whether the video should include microphone audio. A few minutes of preparation can prevent an otherwise useful recording from containing passwords, message previews, or unwanted background noise.
Using The Built-In Screenshot Utility
Recent elementary OS releases include screen recording through the Screenshot application. Open Applications and search for Screenshot, or launch it from the application menu. Depending on your version, the utility may present options for capturing a full display, a selected area, or a window, along with a recording mode.
Select the video or screen-recording option, then choose the region you want to capture. A full-screen recording is suitable for showing a complete workflow, while a selected rectangle is better when you want to focus on one application. If the utility offers a window option, selecting a single window keeps the video cleaner and avoids recording unrelated desktop activity.
Start the capture and perform the actions you want to demonstrate. A recording indicator may appear in the panel or near the edge of the screen. Return to the Screenshot utility or use the displayed stop control to finish. The resulting video is generally saved in your Videos folder, although the exact location and file format can vary between elementary OS versions.
The built-in option is deliberately simple. It is convenient for short clips because there are few settings to configure, but it may not provide detailed control over frame rate, compression, audio sources, or webcam input. If your version of elementary OS does not show a recording mode, use a third-party application instead of assuming that the feature is unavailable system-wide.
Checking Shortcuts And Recording Permissions
Keyboard shortcuts can make native screen capture faster. Open System Settings and inspect the Keyboard or Shortcuts area for entries related to screenshots and screen recording. The exact shortcut depends on the elementary OS release and the installed desktop components, so a shortcut documented for GNOME or another distribution may not work in Pantheon.
A common mistake is to rely on a shortcut from a different Linux desktop. GNOME Shell’s screencast shortcut, for example, is not a universal Linux command. elementary OS uses its own desktop environment and utilities, so verify the assigned key combination locally. If the shortcut conflicts with another action, change it in the keyboard settings or launch Screenshot manually.
Screen sharing and recording can also depend on desktop portals and the active display server. On systems using Wayland, applications usually request permission to access a screen or window through a secure portal. This can produce a selection dialog each time a recording begins. On an X11 session, older recording applications may behave differently, particularly when capturing individual windows or multiple monitors.
If a recorder shows a black screen, captures only a frozen frame, or cannot find an audio device, update the system first. Open AppCenter and install available operating system updates, then restart the session. Problems can also come from unsupported capture methods, missing PipeWire components, or an application that has not been updated for the current display environment.
Choosing A Third-Party Recorder
Kooha is a practical choice for users who want a graphical screen recorder without the complexity of a production suite. It focuses on the essentials: selecting a display or region, choosing whether to capture system audio or a microphone, and saving the result as a common video file. Its uncluttered interface suits short tutorials, bug reports, and demonstrations.
OBS Studio is the most flexible option for advanced recordings and live streaming. It uses scenes and sources, allowing you to combine a desktop, a particular window, a webcam, images, text, and several audio inputs. OBS can record at a chosen resolution and frame rate, apply filters to microphone audio, and save recordings in formats suitable for later editing.
SimpleScreenRecorder offers a more traditional configuration workflow. It can capture a full screen or a selected area, adjust video and audio settings, and provide detailed control over output quality. It may appeal to experienced Linux users who want predictable recording parameters without the broadcast-oriented interface of OBS Studio.
VokoscreenNG is another capable desktop recorder with options for screen regions, windows, audio sources, magnification, and webcam capture. It is useful for instructional videos where highlighting the pointer or showing a camera feed matters. Peek, where available for your release and software sources, is better suited to short animated clips than full-length tutorials.
| Tool | Best For | Audio Options | Advanced Controls | Learning Curve |
|---|---|---|---|---|
| Screenshot | Quick desktop clips | Basic or version-dependent | Minimal | Very low |
| Kooha | Simple tutorials and bug reports | Microphone and system audio options may vary | Few | Low |
| OBS Studio | Tutorials, streaming, and presentations | Multiple sources and filters | Extensive | Moderate to high |
| SimpleScreenRecorder | Detailed local recordings | System and microphone inputs | Strong recording controls | Moderate |
| VokoscreenNG | Guided demonstrations | Microphone, system audio, and webcam options | Moderate | Low to moderate |
Installing Recording Software On elementary OS
Start with AppCenter when the application you need is available there. Search for the application name, review its description and permissions, and install it using your normal user account. AppCenter may provide a Flatpak package, which keeps the application and many of its dependencies separate from core system files.
Flatpak applications can require permission to access the screen, camera, microphone, or home folders. If a program installs successfully but cannot save a recording or detect a webcam, review its permissions with a graphical permission manager or the Flatpak command line. Avoid granting broad access unless the application genuinely needs it.
For software that is not available through AppCenter, use the developer’s official Linux instructions. On Debian-based elementary OS systems, some projects provide a Debian package or an official repository. Check that the package supports your elementary OS release before installing it. Mixing packages intended for another Ubuntu or Debian version can create dependency problems.
OBS Studio is often available as a Flatpak, while other utilities may be distributed through AppCenter or their project websites. Keep the installation source consistent where possible. Installing several versions of the same recorder from unrelated sources can make it difficult to identify which plugins, codecs, and configuration files are being used.
Configuring Video And Audio Quality
Resolution and frame rate determine much of the recording’s appearance and file size. For ordinary desktop tutorials, 1080p at 30 frames per second is usually sufficient when the display and computer can maintain it. A 60 FPS recording produces smoother cursor movement and animation, but it uses more processing power and storage.
The recording format also matters. MKV is a resilient choice during capture because an interrupted recording is less likely to lose the entire file. OBS Studio can remux an MKV file to MP4 after recording, making it easier to use with editors and web services. MP4 is convenient for sharing but can become unusable if the application or computer stops before the file is finalized.
Test audio before making a long recording. Speak for a few seconds and watch the microphone meter. If the meter remains still, select the correct input in the application or System Settings. Keep the microphone level below clipping, which usually appears as a meter reaching the maximum or a harsh, distorted sound in the test clip.
System audio is separate from microphone audio. You may need to choose the desktop output or monitor source explicitly, especially when using Bluetooth headphones or an external sound card. A short test can reveal whether the recording includes application sounds, your voice, both sources, or neither. Disable notification sounds when they are not part of the demonstration.
Making Recordings Look Clear And Professional
Before pressing record, arrange the desktop so the important content is easy to follow. Increase the text size in the application when demonstrating small interface elements, maximize the relevant window, and remove unnecessary panels or tabs. A clean workspace reduces the amount of editing required later.
The pointer should remain visible and move at a deliberate pace. In a recorder that supports cursor highlighting, enable it and choose a subtle size. When that option is unavailable, pause briefly after opening menus or clicking controls. Fast pointer movement is difficult to follow in both a live demonstration and a finished video.
Use a selected recording region when the full desktop adds no useful information. It can hide personal notifications and reduce the final file size. Full-screen capture is preferable when demonstrating workspace switching, panel controls, multi-window workflows, or changes that affect the entire desktop.
Record a short trial before a long session. Play it back and check the image sharpness, cursor visibility, microphone volume, system sounds, and saved file location. This also confirms that the application can maintain the selected frame rate without dropped frames or excessive processor use.
Solving Common Recording Problems
A black or transparent capture often indicates that the chosen capture method does not match the active display server. Try recording the entire display instead of a single window, or select a capture source designed for PipeWire or Wayland. Updating the recorder may also add support for the current elementary OS release.
When the video stutters, reduce the resolution or frame rate and close demanding applications. Browser tabs playing video, virtual machines, games, and large builds can compete with the recorder for processor and graphics resources. Saving to a fast local drive is preferable to recording directly to a slow network location or nearly full disk.
If the file is large, lower the quality gradually rather than making an extreme change. Desktop content contains sharp text, so excessive compression can make menus and terminal output difficult to read. For a tutorial, readable text is usually more valuable than the smallest possible file.
Audio problems need separate diagnosis. Confirm that the microphone is selected, check its input level in System Settings, and verify that another application is not exclusively using the device. Bluetooth headsets can switch between high-quality playback and lower-quality headset modes, so a wired microphone or USB headset may provide more consistent results.
A Practical Recording Workflow
Use this short checklist before important captures:
- Update elementary OS and the recording application before starting.
- Close private conversations, password managers, and unrelated browser tabs.
- Record a brief test with the intended screen area and audio sources.
- Keep several gigabytes of free storage for the video and temporary files.
- Review the finished clip before sharing it publicly.
For a quick support video, the built-in Screenshot utility or Kooha is usually enough. For a narrated tutorial with camera input, multiple windows, or live scene changes, OBS Studio provides the necessary flexibility. SimpleScreenRecorder and VokoscreenNG sit between those choices, offering more configuration while remaining focused on local screen capture.
Organize recordings with descriptive filenames that include the application and date. Keep the original file until the edited or compressed version has been checked. If the video contains sensitive information, trim or blur it before uploading it to a forum, bug tracker, video host, or chat service.
Whether you choose the native utility or a full recording suite, elementary OS gives you a straightforward path from desktop activity to a shareable video. Install the tool that matches the task, test its screen and audio sources, and record a short sample before committing to a longer demonstration. Open the application you prefer and capture your next elementary OS workflow with a clear workspace, readable settings, and reliable audio.