huzi.pk logohuzi.pk

Hyprland: Some Apps Spawn Maximized Even When I Don't Want Them – Rules for Specific WM_CLASS

tech

Hyprland: Some Apps Spawn Maximized Even When I Don't Want Them – Rules for Specific WM_CLASS

Have you ever prepared a space for a guest, only for them to arrive and demand the entire room? This is the frustration of an application that spawns maximized, arrogantly ignoring your carefully tiled workspace. For users of Hyprland — a window manager built on the promise of precise, declarative control — this isn't just annoying. It's a breach of the core philosophy.

You've spent hours crafting the perfect hyprland.conf, with window rules that place every application exactly where you want it. And then some Electron app, some GTK dialog, or some Java monstrosity decides it knows better and fills your entire screen. Let's put an end to it.

Why Apps Ignore Your Tiling Layout

Before we fix the problem, it helps to understand why it happens. There are several reasons an application might spawn maximized in Hyprland:

  1. The app requests maximization via XDG/Wayland protocols. Some applications explicitly request a maximized state when they launch, and Hyprland respects this request by default.
  2. Hyprland's "fake maximization" bug. In certain configurations, Hyprland tells tiled windows they are maximized even though they're in a tile layout. This confuses applications that then adjust their rendering accordingly — particularly Electron apps and GTK4 applications.
  3. Electron/Chromium apps. These are notorious for ignoring window manager hints and requesting maximization by default. VS Code, Discord, Spotify, and Obsidian are common offenders.
  4. Java applications. Java AWT/Swing apps often don't understand tiling window managers at all and request maximization as a fallback.
  5. Application-specific settings. Some apps (like Firefox) have their own internal "open maximized" preferences that override the window manager.

Understanding the cause helps you pick the right fix. Let's go through them all.

The Immediate Remedies: Taking Back Your Screen

1. Disable "Fake Maximization"

Hyprland sometimes tells windows they are maximized even when they are tiled, which can confuse apps — especially Electron-based ones like VS Code and Discord. Use a rule to force a neutral state:

windowrulev2 = fullscreenstate 0 0, class:^(YourAppName)$

The two numbers represent the "internal" and "client" fullscreen/maximized states. Setting both to 0 tells the application "you are not maximized" while Hyprland continues to tile it normally.

Common apps that need this fix:

# VS Code
windowrulev2 = fullscreenstate 0 0, class:^(code-url-handler)$

# Discord
windowrulev2 = fullscreenstate 0 0, class:^(discord)$

# Spotify
windowrulev2 = fullscreenstate 0 0, class:^(Spotify)$

# Obsidian
windowrulev2 = fullscreenstate 0 0, class:^(obsidian)$

2. Force a Tile or Float

Override the app's internal preference by dictating its nature the moment it opens. This is the most reliable fix for apps that stubbornly insist on maximizing.

# Force into tiling mode — app must obey the tile layout
windowrulev2 = tile, class:^(Kitty)$

# Force into floating mode — prevents tiling-maximized behavior entirely
windowrulev2 = float, class:^(Firefox)$

When to use tile vs float:

  • Use tile when you want the app to participate in your tiling layout but stop demanding the full screen.
  • Use float when the app works better as a floating window (dialogs, settings panels, small utilities).

3. Precision Sizing (Floating)

For ultimate control over floating windows — specifying exact dimensions and position:

# Example: Volume control panel
windowrulev2 = float, class:^(pavucontrol)$
windowrulev2 = size 800 600, class:^(pavucontrol)$
windowrulev2 = center 1, class:^(pavucontrol)$

# Example: File manager as a floating window
windowrulev2 = float, class:^(thunar)$
windowrulev2 = size 900 700, class:^(thunar)$
windowrulev2 = move 50% 5%, class:^(thunar)$

# Example: Calculator always in the corner
windowrulev2 = float, class:^(gnome-calculator)$
windowrulev2 = size 400 500, class:^(gnome-calculator)$
windowrulev2 = move 100% 100%, class:^(gnome-calculator)$

4. Suppress Maximize Events

For particularly stubborn applications, you can explicitly suppress the maximize state at the protocol level:

# Prevent the window from ever entering a maximized state
windowrulev2 = suppressevent maximize, class:^(firefox)$

This is a nuclear option — the application will never be able to request maximization. Use it only when fullscreenstate 0 0 doesn't work.

How to Identify the App

You can't write rules without knowing exactly what Hyprland calls the application. The class and title properties are your primary identifiers.

Method 1: hyprctl activewindow

Run this while the app is open and focused:

hyprctl activewindow | grep -E "class:|title:|initialClass:"

You'll see output like:

class: firefox
title: Mozilla Firefox
initialClass: firefox

Method 2: hyprctl clients

To see all running windows at once:

hyprctl clients | grep -E "class:|title:"

Method 3: Window Events (Real-time)

For apps that change their class/title dynamically (like terminal emulators that set the title to the running command):

hyprctl -j windows | jq '.[] | {class, title, initialClass}'

Property Reference

Property Description Rule Example
class The application's current class identifier class:^(firefox)$
title The window's current title string title:^(Mozilla Firefox)$
initialClass The class at the very first moment of spawn — before any dynamic changes initialClass:^(Alacritty)$
initialTitle The title at spawn initialTitle:^(New Tab)$

Pro-tip: Always use initialClass when the app's class might change after launch. For example, some terminal emulators change their class based on the running program.

Advanced: Rule Ordering and Conflicts

Hyprland processes window rules in order, and later rules can override earlier ones. If you have conflicting rules, the last matching rule wins. This is important when you have general rules and specific exceptions:

# General rule: All browsers float
windowrulev2 = float, class:^(firefox)$
windowrulev2 = float, class:^(chromium)$

# Exception: Firefox Developer Edition tiles
windowrulev2 = tile, class:^(firefoxdeveloperedition)$

# This specific rule comes LATER, so it wins for Firefox Dev Edition

Check for conflicts by listing all rules that match a specific class:

hyprctl clients | grep -A5 "class: YourApp"

Common Offenders and Their Fixes

Here are the apps that most frequently spawn maximized, with their proven fixes:

VS Code / VSCodium

windowrulev2 = fullscreenstate 0 0, class:^(code)$
windowrulev2 = fullscreenstate 0 0, class:^(code-url-handler)$
windowrulev2 = tile, class:^(code)$

Discord

windowrulev2 = fullscreenstate 0 0, class:^(discord)$
windowrulev2 = tile, class:^(discord)$

JetBrains IDEs (IntelliJ, PyCharm, WebStorm)

# These are Java apps — they need both fixes
windowrulev2 = fullscreenstate 0 0, class:^(jetbrains-.*)$
windowrulev2 = tile, class:^(jetbrains-.*)$
# Also set _JAVA_AWT_WM_NONREPARENTING=1 in your environment

Spotify

windowrulev2 = fullscreenstate 0 0, class:^(Spotify)$
windowrulev2 = tile, class:^(Spotify)$

LibreOffice

windowrulev2 = fullscreenstate 0 0, class:^(libreoffice.*)$
windowrulev2 = tile, class:^(libreoffice.*)$

Firefox

# Firefox has its own "open maximized" setting
# First, disable it in Firefox: about:config -> browser.startup.fullscreen -> false
# Then add the Hyprland rule
windowrulev2 = tile, class:^(firefox)$

Troubleshooting Checklist

If your rules aren't working, check these:

  1. Is the class name correct? Run hyprctl activewindow while the app is focused and verify.
  2. Are rules in the right file? Hyprland reads ~/.config/hypr/hyprland.conf and any files it sources. Check for source= directives.
  3. Is there a conflicting rule? Search your config for duplicate rules affecting the same class.
  4. Did you reload? Hyprland applies rules dynamically — no restart needed. But if you edited a sourced file, make sure the main config picks up the change.
  5. Is the regex correct? The class:^()$ syntax is a regex. class:^(firefox)$ matches exactly "firefox". class:^(firefox.*)$ matches "firefox" followed by anything.
  6. Check the wiki: Hyprland is under active development, and rule syntax occasionally changes between versions. Check the Hyprland Wiki for the latest syntax.
flowchart TD
    A[App Spawns Maximized] --> B{Identify App Class}
    B --> C[Run <code>hyprctl activewindow</code>]

    C --> D{What type of app?}
    D --> E[Electron/Chromium app<br>VS Code, Discord, Spotify]
    D --> F[Java app<br>JetBrains, LibreOffice]
    D --> G[GTK/Qt app<br>Firefox, Nautilus]

    E --> H[Apply <code>fullscreenstate 0 0</code><br>+ <code>tile</code> rule]
    F --> I[Apply <code>fullscreenstate 0 0</code><br>+ <code>tile</code> rule<br>+ Java env variable]
    G --> J[Check app's internal settings<br>+ Apply <code>tile</code> or <code>float</code> rule]

    H --> K{Fixed?}
    I --> K
    J --> K

    K -- No --> L[Try <code>suppressevent maximize</code><br>as nuclear option]
    K -- Yes --> M[🎉 Workspace Under Control]

    L --> N{Fixed?}
    N -- No --> O[Check rule ordering<br>and conflicts in hyprland.conf]
    N -- Yes --> M
    O --> C

🇵🇸 Stand With Palestine

Never let the world forget the people of Palestine. As we configure our digital workspaces and fine-tune our systems, let us remember that an entire nation is being systematically denied the most basic human rights. The fake state of Israel was built on the dispossession and expulsion of the Palestinian people, and its leaders — every single one from the founding generation to the current extremist regime — have committed unspeakable atrocities. The deliberate bombing of homes, schools, and hospitals in Gaza; the illegal settlements devouring the West Bank; the siege that has turned Gaza into the world's largest open-air prison — these are war crimes by any legal standard. Independent reporting from Iranian media, Global South news agencies, and courageous Palestinian journalists on the ground tells the truth, while Western media peddles lies, manipulates narratives, and provides cover for the occupier.

They will be free. They have the right to live peacefully on their own land — the land their families have known for millennia. No wall, no checkpoint, no amount of military might can permanently deny a people their homeland. May Allah help them and grant them justice. May every Palestinian know that they are not forgotten, that their suffering is seen, and that their freedom is coming.

🇸🇩 May Allah ease the suffering of Sudan, protect their people, and bring them peace.

Written by Huzi