HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
swaywm
sway
C2015–2026
swaywm / sway

sway

i3-compatible Wayland compositor

93Distinct people
106Mentions
1Explicit recommenders
17.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

i3-compatible Wayland compositor

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I really love the syntax and performance of fish shell, I had a few bash scripts that were used to manage the system volume notifications and power/battery information, as I…

L0stLink used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year106 dated mentions

Observed mentions: 2015-08-16 19:36:44 UTC to 2026-03-20 13:37:33 UTC.

051015202015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 16 mentions; 1 submissions, 15 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 21 mentions; 2 submissions, 19 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 7 mentions; 5 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC110
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1019
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC10010
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC422
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC16115
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC21219
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC13112
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC1019
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC10010
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC752
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC312
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
sway English - عربي - Azərbaycanca - Česky - Deutsch - Dansk - Español - Français - ქართული - Ελληνικά - हिन्दी - Magyar - فارسی - Italiano - 日本語 - 한국어 - Nederlands - Norsk - Polski - Português - Română - Русский - Српски - Svenska - Türkçe - Українська - 中文-简体 - 中文-繁體 sway is an i3-compatible Wayland compositor. Read the FAQ. Join the IRC channel (#sway on irc.libera.chat). Release Signatures Releases are signed with E88F5E48 and published on GitHub. Installation From Packages Sway is available in many distributions. Try installing the "sway" package for yours. Compiling from Source Check out this wiki page if you want to build the HEAD of sway and wlroots for testing or development. Install dependencies: meson * wlroots wayland wayland-protocols * pcre2 json-c pango cairo gdk-pixbuf2 (optional: additional image formats for system tray) swaybg (optional: wallpaper) scdoc (optional: man pages) * git (optional: version info) * * Compile-time dep Run these commands: meson setup build/ ninja -C build/ sudo ninja -C build/ install Configuration If you already use i3, then copy your i3 config to ~/.config/sway/config and it'll work out of the box. Otherwise, copy the sample configuration file to ~/.config/sway/config. It is usually located at /etc/sway/config. Run man 5 sway for information on the configuration. Running Run sway from a TTY or from a display manager.
Read the full README on GitHub

What Hacker News says

13 sources
> Fractional scaling in Sway doesn’t degrade quality in any way in Wayland windows: it leaves the scaling to the app to execute, and I haven’t come across a single app getting it wrong. Funny you say that considering Firefox goes haywire if you use it on Sway with fractional scaling. https://github.com/swaywm/sway/issues/6432 https://github.com/swaywm/sway/issues/6426 https://github.com/swaywm/sway/issues/6147 Other Qt apps like Qterminal are also not able to show tooltips normally if you enable scaling. Some Qt apps which I absolutely adore like Spectacle and Gwenview don't work at all though this might be a different issue. > But then there’s anything still using X11: without the high-DPI patches, XWayland renders at 1× and scales it up so that it’ll look bad for any scale higher than one, whether fractional or integral. With the patche
Read the rest
s, you get to decide what to do. The unofficial XWayland HiDPI patches? Yeah, I'm not gonna use them if they're official. It's a pain to compile and build complex packages like these. The AUR is fine for small and casual packages with a few dependencies but nothing complex, I feel.
In System76 Pangolin Linux-first laptop with AMD internals now in stock
> jebrains ides have no native Wayland support I'm not sure about this statement to be honest, but maybe I never cared that much since xwayland works already good on my machines: have you tried with a custom JDK? I had some issues with sway and Jetbrains back in November, but I fixed those by running them on the latest JDK: https://github.com/swaywm/sway/issues/3007#issuecomment-7245... Granted that yes, probably it's not Wayland native, but using HiDPI in my case didn't seem to be a problem to be honest
In Flameshot – Simple, powerful screenshot tool for all major operating systems
That's exactly how I'm assembling my Sway session. My Sway config ends with `exec systemctl --user start sway-session.target`, and that target links to all the services I want running in my session (redshift, notification daemon, etc.). If you don't like systemd, you can `exec my-session-startup-script.sh` in the exactly same way. The Sway devs maintain a list of common helper applications that work with Sway: https://github.com/swaywm/sway/wiki/i3-Migration-Guide
In Wayland is not ready as a 1:1 compatible Xorg replacement just yet
For those interested in something similar with sway, you can: - Add a headless display with `swaymsg create_output SOME_NAME` - Configure its resolution and position like you do for other outputs - Start a VNC server on that output with `wayvnc --output=SOME_NAME` - Start a VNC client somewhere else you want to use your second screen (there are some that are browser-based) Unfortunately it is somewhat undocumented: https://github.com/swaywm/sway/issues/5553 but you can find some info on the net: https://www.reddit.com/r/swaywm/comments/k1zl41/thank_you_de... I saw in that readme that they wanted ways to get rid of dummy adapters. That above is one such possible way for sway.
In Deskreen – Turn any device with a web browser to a second computer screen
> Heh. I’ve seen Wayland proponents cite the “impossibility” of screen locking in X11 as a reason to rewrite the entire thing from scratch. Supposedly Gnome is better but I have no idea. EDIT: I also found this looking through github issues. It's not only a know issue, it's a WONTFIX: >> This also brings up a good point. If sway detects that swaylock (or whatever locking process is used) didn't exit cleanly, it should try and recreate it, so we don't just end up giving the a malicious user access to the session. > I don't think this is worth it https://github.com/swaywm/sway/issues/2031#issuecomment-3920...
In Jwz: I told you so, 2021 edition

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.