# Fullscreen or borderless window for games?

**URL:** <http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154>\
**Category:** General\
**Tags:** question\
**Created:** [July 23, 2025, 1:25pm UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154 "2025-07-23T13:25:19Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![nico](http://forum.hypr.land/letter_avatar_proxy/v4/letter/n/b5a626/32.png) [@nico](http://forum.hypr.land/u/nico)\
**Post date:** [July 23, 2025, 1:25pm UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/1 "2025-07-23T13:25:19Z")

</div>

Which is better? Is there any difference between them under Hyprland?

I use borderless right now because most games seem to default to that but I have no idea why I would use one over the other.

---

<div class="post-metadata">

**Author:** ![vaxry](http://forum.hypr.land/user_avatar/forum.hypr.land/vaxry/32/3_2.png) [@vaxry](http://forum.hypr.land/u/vaxry)\
**Post date:** [July 23, 2025, 9:13pm UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/2 "2025-07-23T21:13:44Z")

</div>

No difference, if you fullscreen a borderless window it’s the same as fullscreen. Only difference might be in how the game treats itself, in which case usually borderless will win because then the game won’t try to fullscreen itself when you unfullscreen it for whatever reason you might want it.

---

<div class="post-metadata">

**Author:** ![sleroq](http://forum.hypr.land/user_avatar/forum.hypr.land/sleroq/32/266_2.png) [@sleroq](http://forum.hypr.land/u/sleroq)\
**Post date:** [July 24, 2025, 9:19am UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/3 "2025-07-24T09:19:15Z")

</div>

With fullscreen window you can use `immediate` window rule which can significantly reduce input lag by enabling tearing. - [Tearing – Hyprland Wiki](https://wiki.hypr.land/Configuring/Tearing/)

I use it for osu! and fps games.

---

<div class="post-metadata">

**Author:** ![vaxry](http://forum.hypr.land/user_avatar/forum.hypr.land/vaxry/32/3_2.png) [@vaxry](http://forum.hypr.land/u/vaxry)\
**Post date:** [July 24, 2025, 9:54am UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/4 "2025-07-24T09:54:45Z")

</div>

if you fullscreen a borderless window manually via a keybind you can use it too.

---

<div class="post-metadata">

**Author:** ![fazzi](http://forum.hypr.land/user_avatar/forum.hypr.land/fazzi/32/270_2.png) [@fazzi](http://forum.hypr.land/u/fazzi)\
**Post date:** [July 27, 2025, 7:41am UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/5 "2025-07-27T07:41:49Z")

</div>

Borderless full screen works better for me in pretty much every instance where it’s available. On multi monitor setups, a game in full screen usually goes black when switching focus to your secondary monitor, so borderless wins in that scenario.

---

<div class="post-metadata">

**Author:** ![vaxry](http://forum.hypr.land/user_avatar/forum.hypr.land/vaxry/32/3_2.png) [@vaxry](http://forum.hypr.land/u/vaxry)\
**Post date:** [July 27, 2025, 1:19pm UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/6 "2025-07-27T13:19:54Z")

</div>

Usually a remnant of Windows games. Well, the distinction in general is very windows-y.

The reason is Windows “exclusive fullscreen” gives the app _direct_ control of the display. Like, down to the gpu direct. That’s why games can often force your display to modeset (2s of black screen, weird resolutions, etc)

On Wayland, no such mechanism exists. The app can never have direct drm access, so the difference between “fullscreen” and “borderless” is pretty much non-existent outside of the app’s minor window-management-stuff behavior. (e.g. “if I am in fullscreen, I’ll ask the compositor to make me fullscreen”)

---

<div class="post-metadata">

**Author:** ![nico](http://forum.hypr.land/letter_avatar_proxy/v4/letter/n/b5a626/32.png) [@nico](http://forum.hypr.land/u/nico)\
**Post date:** [July 27, 2025, 7:12pm UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/7 "2025-07-27T19:12:41Z")

</div>

Am I doing this right?

```auto
general {
    allow_tearing = true
}

...

bind = $mod, F, fullscreen, immediate

```

---

<div class="post-metadata">

**Author:** ![vaxry](http://forum.hypr.land/user_avatar/forum.hypr.land/vaxry/32/3_2.png) [@vaxry](http://forum.hypr.land/u/vaxry)\
**Post date:** [July 27, 2025, 7:57pm UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/8 "2025-07-27T19:57:22Z")

</div>

> [@nico](#):
>
> `bind = $mod, F, fullscreen, immediate`

`immediate` is a windowrule, not a dispatcher parameter.

---

<div class="post-metadata">

**Author:** ![nico](http://forum.hypr.land/letter_avatar_proxy/v4/letter/n/b5a626/32.png) [@nico](http://forum.hypr.land/u/nico)\
**Post date:** [July 27, 2025, 8:56pm UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/9 "2025-07-27T20:56:13Z")

</div>

```auto
windowrule = immediate, fullscreen:1

```

?  
is `hyprctl clients` supposed to show something when tearing is enabled for a window?

---

<div class="post-metadata">

**Author:** ![vaxry](http://forum.hypr.land/user_avatar/forum.hypr.land/vaxry/32/3_2.png) [@vaxry](http://forum.hypr.land/u/vaxry)\
**Post date:** [July 27, 2025, 9:40pm UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/10 "2025-07-27T21:40:14Z")

</div>

Nope, `hyprctl monitors` will though when tearing is active.  
 ![20250727_23h40m06s](http://forum.hypr.land/uploads/default/original/1X/dc8edfc949aa18e98e5beff180d288b69964d5d5.png)

(and yes the windowrule is ok)

---

<div class="post-metadata">

**Author:** ![furthermoreout](http://forum.hypr.land/letter_avatar_proxy/v4/letter/f/3ec8ea/32.png) [@furthermoreout](http://forum.hypr.land/u/furthermoreout)\
**Post date:** [July 29, 2025, 8:55pm UTC](http://forum.hypr.land/t/fullscreen-or-borderless-window-for-games/154/11 "2025-07-29T20:55:59Z")

</div>

I set them to full screen because I thought that would work the same way it works for Windows as @vaxry described. Silly me…

Any how, this is what I have in `custom.d/regular/rules.conf`

```conf
windowrule = content game, class:^(steam_app_\d+)|gamescope$, title:negative:|^(?i)(.*(Launcher|NetEase Game Security).*)$
windowrule = fullscreen, content:game
windowrule = immediate, content:game

```
