I am working on a 7z GUI for Linux and I am coming here to share it with you all. This is a work in progress and will be getting a bunch of update over the next couple weeks as I look to publish on Flathub soon.
Right now a lot of it is wired up, and ready to go but needs some features to make it stand out. I will be working on this to get to a comfy state to release then worry about the more fancy stuff over time.
Maybe wait a couple days as I get closer to publishing fully on Github Pages, but if you are interested in the development take a peek !
Getting closer to release on flathub, I’ve added a cool feature for verifying hashes. Hash Calculator !
You can get the hashes of your archives and also verify those of .iso or archives you’ve downloaded off the internet. CHECKSUM files for iso’s are present for all major distros and it’s just convenient to verify this way.
There are some other nice to have’s here, like “Transparent nested browsing” & “Transparent nested extract” setting up .tar files + compression in one go, and multi level view of .tar + .zstd files.
Thank you, would you be able (and willing) to switch from the very specific GNOME style of application UI design to something more “industry standard”?
Buttons in the window title is not a well-thought thing. There is lots of room inside the window to place buttons and menus. The title bar of a window belongs to the operating system or window manager, not the application. Imagine you have a tiling window manager which does not show the window title bar, those buttons would be gone / not accessible.
The same applies for regular window managers and anything “full screen”, which does not show the title bar either. The application is useless in situations like this. Not sure why, but recent MS Windows UI design also makes this mistake. MS introduced what they call “WinUI”, which is being used by Win11 and its task manager / notepad e.g.. These applications also don’t comply to colours being set for the active window and it’s title bar e.g., the same is true for what your application is doing right now.
Here is a snapshot of how “out of place” this GNOME (or whatever it actually is) style looks like on a regular desktop with regular windows. The window “in the middle” is not respecting UI style. You cannot see whether its active or not either, because the title bar does not change as the other regular windows.
Thanks for your comment, but I’m going to decline engaging in GUI talk. I’ve had this conversation over and over for 15yrs ( since I personally left Linux ) and do not wish to litigate it again. Some of those conversations are here in this forum !
Thanks again for your comment I truly appreciate it.
I will continue to update this thread with screenshots of the build, I’m going to publish on Friday on Github Pages. Updates will flow from there.
Side Note: I’ve also started work reviving Gradience, and work on a Rsync GUI, and a modern GPU Powered Image Gallery tool in the vein of gThumb. . .
So, you left Linux and still work on tools for this platform?! o) I am not a Linux user either. The visual appearance of UI frameworks and lots of tools is not where I expect things to be in 2026, I just tried to help on the general situation here to get some industry and accessibility standards rolling..
Thank you for taking the time! o)
Offtopic, ps: Please consider to put screenshots of your programs in the readme of your git repos. I always wonder why people do GUI tools without any kind of preview in the repo itself (especially if there is no website either). Since many programs have similar names, it helps to determine the actual (correct) tool, just by the looks and layout. I guess most people also don’t want to download / compile / install a tool they don’t know how it looks or maybe just to see how it looks?
I’m currently doing performance testing, and will be covering that around Friday of this week. I’ve been adding features and all and have been caught up with other things.
We are LIVE ! Anyone looking to test this application can download the flatpak (auto updating included) from the Github. A Modern 7z ZS GUI for those looking to have more than just command line tool !
I was getting “septicemia” from it. I quite like Septima though although it doesn’t indicate to me that it has anything to do with compression software.
If I saw it in a list of software I’d not put it on a mental list that I should install it.
Naming things is hard… Actually stick a 6 in the name, and you have the “naming things is hard” and an “off-by-one error” in one name! Put the 6 in the middle and there’s a “buffer overflow” too…
That looks nice! As the primary maintainer of the 7zip package right now - I regretfully sunsetted p7zip because it has not been maintained for… 10 years now. But the lack of a proper GUI is a bit of sore point for users who were used to it from p7zip.
If you’d like help packaging the GUI, do let me know!
Thanks ! Forgive the theme it’s my own. it’s GTK4/libadwaita/gtk-rs wrapped around 7Z ZS. I absolutely need to have 7z, I’ve been using it for over a decade and having the p7zip not be upgraded and all the issues we had, was the straw for me. People I know always asked for me to do something about the GUI, but time was always an issue + a moving target.
I think I solved both for me at least. a flatpak with proper sandboxing, a checksum creator/verify mechanism and the full 7Z ZS experience.
Right now it’s only flatpak, it works ! So I’m not too focused on repacking as .rpm or any others.
That’s interesting, I have a similar project. called Vivid Gradience. it’s basically a successor to Gradience. This isn’t a file archiver, but thanks for the link.
Unique password per archive. In batch mode (“create a separate archive for each item”), every archive can get its own random 64-character password. The set is recorded in a passwords file you save wherever you keep secrets.
The passwords file is just a file — readable JSON with one entry per archive: the archive name, what it was made from, the password, its SHA-256, when it was written, and the cipher in plain words (“7z, AES-256, encrypted headers”). Keep it in KeePassXC, Bitwarden, pass, a vault, or a drawer. Septima never talks to a password manager’s API, so all of them work by default.
Optional protection for that file — standard symmetric OpenPGP (gpg -c), so any gpg anywhere can open it: no keys, no keyring, no host access. You choose before the run starts, which is what keeps a protected run from ever writing plaintext to disk. Declining shows a plain-words warning instead of silently leaving secrets next to the archives.
Crash-safe by ordering. Every password is written to disk before the first archive is created, and the file is rewritten atomically as each archive completes. An interrupted run can leave a password with no archive; it can never leave an archive with no password.
Batch decrypt — the other half. Open a passwords file with the Open button, by dropping it on the window, or from the command line, and Septima offers to extract every archive it lists, each with its recorded password, into its own folder. A per-entry picker (with select-all, clear, and a filter once the list gets long) means you can take just the ones you want. Missing archives and empty passwords are skipped loudly, and only basenames are trusted, so a hand-edited path can’t walk out of the folder.
Drag entries out to extract — the missing half of drag and drop. Select rows in an open archive, drag them into Files or any app that accepts files, and they arrive extracted. A directory brings its whole subtree.
For those who have installed a simple flatpak update gets you what you need.