Adjust Screen Brightness in Ubuntu: Settings and Terminal Fixes

Illustrated infographic summarizing: Adjust Screen Brightness Ubuntu 19.10 - 22.04

By Greg Nowak. Last updated 2026-11-04.

A screen that is too bright makes everyday work uncomfortable, whether you are reviewing a website, working through spreadsheets, or setting up a shared workstation. In Ubuntu, the right fix depends on the display and your desktop session.

This guide expands the original Ubuntu 19.10–22.04 terminal tip. The xrandr commands remain useful on compatible X11 sessions, but they adjust the image in software. For everyday use, start with the screen’s hardware brightness controls.

How to change brightness in Ubuntu: the short answer

To increase or decrease brightness in Ubuntu, open the system menu at the top right of the screen and drag the brightness slider, or press the brightness keys on a laptop keyboard (often together with Fn). Both change the real backlight. From a terminal on a laptop:

brightnessctl set +10%    # brighter
brightnessctl set 10%-    # dimmer
brightnessctl set 40%     # a fixed level

On an external monitor, use its own buttons, or ddcutil setvcp 10 50 if the monitor supports DDC/CI. If the screen is still too bright at the lowest setting, xrandr --brightness can dim the picture further in an X11 session, and Night Light under Settings > Displays makes it warmer in the evening. Each method is explained below.

Start with Ubuntu’s brightness controls

On the standard Ubuntu desktop, open the system menu at the top right and look for the brightness slider. Laptop keyboards usually have brightness keys marked with a sun icon; depending on the keyboard, you may need to hold Fn. These are the first methods described in Ubuntu’s brightness guide.

For an external monitor, try its physical buttons or joystick and open its on-screen menu. A missing Ubuntu slider does not necessarily mean the monitor’s brightness cannot be changed.

Your situation Start here What to expect
Laptop with working brightness controls Desktop slider or keyboard keys The simplest adjustment for daily use
Laptop needing terminal control brightnessctl Hardware adjustment if Linux exposes a backlight device
External monitor Monitor menu, then ddcutil Software control depends on monitor and connection support
X11 session needing temporary dimming xrandr --brightness Software dimming without lowering the backlight
Wayland session Desktop controls or supported hardware tools The X11 workaround below is unsuitable

Check your session before using xrandr

Open a terminal within your desktop session and run:

echo "$XDG_SESSION_TYPE"

If the result is x11, you can try the next section. If it is wayland, use the hardware methods further down. If the result is blank, check your desktop’s system information before proceeding.

On Wayland, xrandr may still list outputs through the Xwayland compatibility layer. That does not give it control over the physical display configuration, as the Fedora Project’s Wayland documentation explains. A successful listing alone is therefore insufficient.

Dim the image with xrandr on X11

Find the connected display names:

xrandr -q | grep " connected"

For example:

eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 173mm

Here, the display name is eDP-1. Replace it below with your own output name. Start with a modest adjustment:

xrandr --output eDP-1 --brightness 0.8

For stronger dimming, the original command is:

xrandr --output eDP-1 --brightness 0.5

Restore the normal multiplier with:

xrandr --output eDP-1 --brightness 1

The xrandr manual defines this as a software adjustment to gamma values. A value of 0.5 does not mean half the physical backlight brightness; 1 removes this dimming multiplier rather than setting the hardware to maximum.

Avoid this workaround when judging client artwork or website colours. Treat it as a temporary adjustment: desktop colour management or session changes may override it.

Control a laptop backlight from the terminal

When Linux exposes a supported backlight device, brightnessctl provides terminal control without depending on X11. Install it and list the backlight devices:

sudo apt install brightnessctl
brightnessctl --class=backlight --list

If one suitable device appears, inspect its current setting, then set it to 50%:

brightnessctl --class=backlight info
brightnessctl --class=backlight set 50%

Unlike the xrandr multiplier, this percentage refers to the device’s maximum brightness value, as documented in the brightnessctl manual. Record the previous value so you can restore it.

If several devices appear, add --device=DEVICE_NAME using the appropriate name from the listing. If no backlight appears, this method cannot control your panel through that interface. A permission error is a separate issue: on a managed work machine, ask your administrator to check device access before building a shortcut around it.

Adjust an external monitor with ddcutil

For a compatible external monitor, ddcutil can change brightness through DDC/CI. Enable DDC/CI in the monitor’s menu if that option exists, then install the tool and check detection:

sudo apt install ddcutil
ddcutil detect

Use the display number reported for the intended monitor. For display 1, read its brightness first:

ddcutil --display 1 getvcp 10

Record the current value and check the reported maximum. If the maximum is 100, this sets the brightness value to 50:

ddcutil --display 1 setvcp 10 50

Feature code 10 identifies brightness; the ddcutil command overview documents detection, monitor selection, and reading or changing features. If detection fails, use the monitor’s own controls while checking DDC/CI support, connection compatibility, and device permissions.

Make the fix useful for the whole team

Before adding a command to startup, test it after a logout, reboot, and dock reconnection. Record the Ubuntu version, session type, display identifier, working command, and recovery setting. That small handover note helps the next person resolve the same issue without repeating the investigation.

If recurring technical workarounds are interrupting your team’s day, talk to Greg about troubleshooting the setup and documenting a maintainable fix.

Quick answers

Why is there no brightness slider?

Ubuntu shows the slider when it finds a backlight it can control. A desktop PC with only an external monitor often has none, because the monitor sets its own brightness. On a laptop, run ls /sys/class/backlight: an empty folder means the kernel exposes no backlight, which usually points at the graphics driver.

How do I reduce brightness below the minimum?

The backlight stops at its lowest step. To go darker in an X11 session, dim the picture with xrandr --output eDP-1 --brightness 0.7 (take the output name from xrandr -q) and undo it with --brightness 1. It darkens the image, not the backlight, so it saves no power.

Can brightnessctl turn the screen off by accident?

Not with a relative step: brightnessctl set 10%- stops at a minimum value of 1 by default (the -n option). A fixed set 0 can make some panels go dark, so keep a brightness key or brightnessctl set 50% ready.

Does this work on Ubuntu 24.04 and 26.04?

The slider, the keys, brightnessctl and ddcutil do. Both releases start a Wayland session by default, where xrandr --brightness does nothing useful, so check echo "$XDG_SESSION_TYPE" before you try it.

Related on GrN.dk

Need help with this kind of work?

Talk to Greg about your team’s technical setup Get in touch with Greg.

Sources

Latest articles

Build a refund approval workflow in n8n and Stripe that shows reviewers the exact action, expires old approvals and tracks refunds through to completion.

A timeout can hide a successful job creation. Use stable operation IDs, destination API rules and a clear recovery process to prevent duplicate work.

Does your ChatGPT subscription cover website translation? Understand API credits, access and a WordPress workflow that turns approved Danish content into translation drafts.

An internal AI can keep quoting a deleted policy. Check document updates, indexed passages and cached answers to find where outdated guidance survives.

Codex drew all ten pages of my Ninjai comic from the script Claude wrote in the first test. What made that handover work, and what it cost.

ChatGPT delivered ten painted comic pages; Claude drew one page in code. A practical look at AI tool selection, creative briefs and approval decisions.

Get missing supporting documents under control with a clearly scoped AI workflow that sorts replies, coordinates reminders and gives the bookkeeper a clear follow-up list.

Know what dmesg and journalctl can tell you after a reboot, how to find previous-boot logs, and how to check that retention covers your investigation window.

Check how your chatbot identifies itself as AI, where requests for human help actually go, and what customers encounter when support is unavailable.

Start with one website change on board.nowa.dk. Write a clear task, answer questions as they arise and review the result before giving an AI agent more work.