Community-driven coverage of elementary OS — news, guides & forums
Dark abstract low-poly geometric landscape with layered triangular facets in deep navy, charcoal, and muted teal, illuminated by a soft electric-blue glow near the horizon

News roundups, tutorials, application guides, and forums — built by users, for users of the elegant Linux distribution.

elementary weekly
#20
Latest roundup · 18 Apr 2015
Freya Release
Final
Covered in weekly #19 & #20
Forum Topics
Active
Installation, customization & more

Using Elementary OS’s Built-In Screen Recorder

A screen recording is useful when a screenshot cannot show the full problem. You can demonstrate an application bug, create a short software tutorial, record a desktop workflow, or capture a presentation for later review. Elementary OS includes a lightweight recording method through its desktop screenshot interface, so many everyday recordings can be made without installing OBS Studio or another large application.

The exact appearance and available controls depend on your elementary OS release and whether the session uses Wayland or X11. Recent versions place screen capture and screen recording in the same system interface, while older installations may expose fewer options. The steps below focus on the built-in workflow and explain what to check when a shortcut or recording option is missing.

Check Your Elementary OS Version And Session

Before recording, open System Settings and select About to identify your elementary OS release. This matters because keyboard shortcuts, the screenshot panel, and audio support have changed between releases. Install available system updates first, since capture tools are closely connected to the desktop shell and display server.

It is also useful to identify your display session. Open System Settings, choose Desktop, and look for the session or windowing information available on your installation. Wayland-based sessions generally provide safer, application-aware screen capture through desktop portals. X11 sessions can behave differently, particularly with multiple displays, application windows, and hardware-accelerated programs.

Close private notifications and unnecessary windows before you begin. A recording can include anything visible on the selected screen, including message previews, account information, browser tabs, and desktop notifications. If the demonstration includes personal data, create a clean test account or hide sensitive content in advance.

Open The Screen Recording Tool

The quickest method is to press the Print Screen key. On many elementary OS versions, this opens the screenshot and screen capture interface. If your keyboard has no dedicated Print Screen key, search the Applications menu for Screenshot, or open the system settings for keyboard shortcuts and locate the capture action.

The panel normally offers a choice between taking a still image and recording video. Look for a camcorder, video, or recording control rather than the camera option. Depending on the release, you may see controls for the entire display, a selected area, or a particular application window.

Some versions use a keyboard shortcut such as Super + Shift + R to start screen recording directly. The Super key is usually the key with the Windows logo. Shortcuts can be changed by the user or differ between releases, so treat this combination as a useful possibility rather than a universal rule. If it does nothing, use the visible capture interface or inspect the shortcut settings.

When the recorder is ready, select the recording mode before pressing the final start button. A brief countdown may appear, giving you time to open the application or arrange the desktop. If there is no countdown, start from a quiet screen and move to the demonstration only after the recording indicator appears.

Select The Area You Want To Capture

Full-screen capture is the simplest choice for a tutorial that moves between several applications. It records everything on the selected display, including the panel, dock, window borders, and pointer if the recorder supports pointer capture. On a multi-monitor setup, confirm which display is highlighted before starting.

A selected-region recording is better for a short demonstration, bug report, or privacy-sensitive task. Drag across the part of the screen that should appear in the video, then adjust the edges before confirming. Leave enough space around buttons, menus, and dialog boxes that viewers can understand what you are doing.

Window capture, when offered by your release, can produce a cleaner result because it follows one application rather than the whole desktop. It may be unavailable for some applications or under some display-server configurations. If the window option fails, switch to a selected region and include the application’s title bar so the result remains clear.

Keep the target area at a practical resolution. A very small region can make text unreadable after the video is uploaded or embedded on a website. Conversely, recording an entire high-resolution monitor creates larger files and may place unnecessary demands on the graphics processor.

Capture choice Best use Main benefit Possible limitation
Entire display Walkthroughs involving several applications Simple setup and complete context May reveal notifications or private windows
Selected region Bug reports and focused demonstrations Keeps attention on one area Requires careful framing
Application window Single-app tutorials Clean, consistent presentation Availability varies by session and release
Multiple displays Broad desktop demonstrations Shows a large workspace Produces a larger video and can reduce performance

Start, Pause, And Stop The Recording

After choosing the display or region, activate the record button. Watch for a small recording indicator in the panel or system area. That indicator confirms that the desktop is being captured. Moving the pointer briefly can help verify that the recording has started, but avoid unnecessary movements if you are creating a polished tutorial.

Elementary OS’s built-in recorder is designed for straightforward capture rather than studio production. It may provide little or no control over frame rate, bitrate, resolution scaling, webcam overlays, or scene switching. For a quick software demonstration, that simplicity is an advantage. For a presentation with multiple sources, a camera feed, or live transitions, a dedicated application may be more appropriate.

Stop the recording through the visible recording indicator or the shortcut shown by the capture interface. If the desktop provides a pause control, use it to remove long periods of waiting from the final file. Do not force-close the screenshot utility or shut down the computer while recording, because the video may not be finalized correctly.

Give the system a moment after stopping. The recorder needs to write the video container and close the file. Opening the destination immediately is usually safe after the recording notification appears, but a large capture on a slower drive may take longer.

Understand Audio And Recording Quality

Screen capture and audio capture are separate concerns. Some elementary OS versions record the visual desktop without microphone or system audio controls. Others may expose audio choices through the desktop portal or a permissions dialog. Before making an important recording, create a ten-second test and play it back with headphones.

If the microphone is available, check the input device in System Settings under the sound controls. Select the intended microphone, speak at a normal volume, and watch for an input level indicator if one is provided. A USB headset, laptop microphone, and webcam microphone can produce very different results, so verify the selected source rather than assuming the default is correct.

System audio may not be included by the built-in tool, especially when the recorder exposes no audio menu. In that situation, explain application sounds with narration, use subtitles, or capture the audio separately with an approved utility. Avoid routing audio through improvised virtual devices unless you understand the consequences for other applications.

Performance also affects the result. Close demanding programs, pause large downloads, and connect a laptop to power. Hardware-accelerated applications, games, virtual machines, and high-resolution displays may produce dropped frames or a sluggish desktop. A short test recording reveals these problems before they affect the full demonstration.

Find, Review, And Share The Video

When recording ends, elementary OS generally saves the video in the Videos folder or another location defined by the capture utility. Open the Files application and check Videos, Home, and the recent-files view. The filename usually includes a date or time, which helps distinguish several test captures.

Open the file with the default video player and inspect the entire recording. Confirm that the correct region was captured, the text is readable, the pointer appears where expected, and audio is present if you intended to record it. Check the beginning and end especially carefully because a countdown, a premature stop, or a blank frame can make a tutorial look unfinished.

The built-in recorder may save a web-friendly format such as WebM, although the exact format depends on your elementary OS release and installed multimedia support. WebM is efficient for browser playback, while some editing programs and workplace platforms prefer MP4. Do not rename a file extension without converting the file; changing the name alone does not change its encoding.

For trimming, subtitles, format conversion, or audio cleanup, use a separate editor after the capture is complete. A simple editor can remove the countdown and pauses without reworking the entire recording. Keep the original file until the edited version has been checked, particularly if the video documents a software fault or configuration problem.

Resolve Common Recording Problems

If pressing Print Screen opens only a still-image mode, check for a separate video control in the same panel. Review keyboard shortcuts in System Settings and search for terms such as screenshot, screen capture, or screen recording. A missing recording option may indicate an older elementary OS release or a desktop session that does not provide the required capture portal.

A blank or black recording is often related to the display server, protected video content, or an application using a rendering method the recorder cannot capture. Test the desktop, Files application, and a normal window first. If those work but one program remains black, the limitation may belong to that program rather than the recorder.

When the video contains no sound, inspect the audio permissions and input device, then repeat a short test. Some releases simply do not support microphone or system audio in the built-in tool. A distorted recording can result from an overloaded CPU, a busy disk, or a microphone level set too high.

For failed or incomplete files, make the next test shorter and reduce the capture area. Save recordings to a drive with free space, close resource-heavy applications, and avoid suspending the computer during capture. If built-in recording remains unsuitable, an application such as OBS Studio can provide detailed control over sources, encoders, audio tracks, and scenes.

Practical Settings For Better Captures

Use these habits for more reliable elementary OS screen recordings:

  • Prepare the desktop first by hiding private notifications, closing unrelated windows, and arranging the target application.
  • Record a short test to confirm the selected area, pointer behavior, microphone input, and saved file location.
  • Prefer a selected region for focused tutorials, but include enough surrounding interface for viewers to identify menus and controls.
  • Keep demonstrations concise and pause briefly before important actions so the recording is easier to trim and understand.
  • Preserve the original video until playback, editing, and upload checks are complete.

A built-in recorder works best when the goal is clarity rather than production complexity. It can document a reproducible bug, show a configuration step, or explain an elementary OS workflow with very little setup. Its limits become apparent when you need multiple audio tracks, webcam footage, precise encoding controls, or advanced editing, but those needs do not apply to every desktop capture.

Try a short recording now using a harmless application such as Files or System Settings. Review the saved video, note which capture controls your elementary OS release provides, and then use the same workflow for tutorials, support requests, and community discussions on elementarynow.

Browse the News Archive
Latest Updates

From the elementary weekly series

Low-poly faceted abstract render in dark charcoal and electric blue tones, suggesting a news bulletin or announcement
elementary news

elementary weekly #20

The first week with the final Freya release — community reactions, tips, and early impressions gathered in one roundup.

Abstract low-poly geometric scene in midnight blue and soft cyan, conveying a live broadcast or event atmosphere
elementary news

elementary SPECIAL

A live Hangouts event with the elementary OS founders, held on 11 April 2015, discussing the Freya final release.

Low-poly faceted render in deep navy and muted teal with subtle amber highlights, suggesting a tutorial or guide
Tips and Tricks

Timeshift Guide

How to use Timeshift — the intuitive system restore utility for elementary OS — to recover from configuration mishaps.

Explore

Topics & Resources

Dive into guides, application recommendations, and community discussions covering every aspect of elementary OS.