Skip to main content


Flatpaks are really outrageous in size...I have tried to use flatpaks for the past months but man o man....hundreds of MB for each package, takes forever to update them even on my 1GB internet connection. The idea is great, but this is such a huge downside that I cannot see how it is going to make the flatpaks easier to use than normal packaging.

Look at this for ungoogled chromium:

Had to download around 4-5 GB....insane!

#linux #flatpak

Rokosun reshared this.

in reply to Tio

probably really depends on your usecase. For my slow internet connection, I really love how Flatpaks are an exception to the "partial upgrades are not supported" problem. Just because I need to install discord it does not mean that I want to do a 2,3GB update to my system, my friend is waiting for me.
in reply to Tio

I like these containerized apps but they are pain in the ass sometimes, really. However, this is future. Like it or not; Ubuntu is moving away from *.deb, more and more distros will act similarly. Just hope that Flatpak will win this fight and not Snap, and it will be fine...
in reply to Florke×64 🏴‍☠️

@florke64 Why do you think native packages are going away? Especially when flatpaks has all these downsides like taking too much space and not respecting the user's theme or integrating well with the system. Flatpak is there as an option but you don't need to use it if you don't want to, I personally never use it and I'm fine..... 🤷 I'm not sure about Ubuntu tho 'cause I'm on Arch, but I'd be surprised if Debian ever gets rid of native packaging.
in reply to Rokosun

@futureisfoss @florke64 easy of use. Flatpaks are much easier to use for the average 'new to linux' user. Plus they actually have a proper permission system (flatseal) unlike native packages.
in reply to Thibault Molleman🇧🇪 🌈🐝

@thibaultmol @florke64 I'm not sure about ease of use because most GUI distros have a software center these days for installing native and flatpak apps - so both are easy now. The permission system is interesting and could have some privacy/security improvements, but this containerization can also create issues with theming and such. A friend of mine recently had issues with playing games on Bottles because of flatpak's sandboxing - so in certain situations it can get in your way.
in reply to Rokosun

@futureisfoss Interesting points. Inconveniences like theming are going to improve over time. Transition will happen gradually. I don't see Debian dropping *.deb support. However, I can imagine Debian shipping Flatpak applications.
in reply to Florke×64 🏴‍☠️

@florke64 Yeah I think the most likely scenario is native packaging and Flatpaks coexisting - which is already the case for most distros now.
in reply to Tio

A lot of those sizes are a worse case scenario. If you have shared requirements with other installed apps, flatpak will deduplacate requirement and save space.
in reply to Hydrian

I understand....but to take 4-5GB to update ungoogled chromium it is insane....
in reply to Tio

Sometimes it is just bad packagers not cleaning up the builds. I package with flatpak, mainly legacy applications, and mine never usually get that explosive in size. Chromium is about 350MB installed with apt.
in reply to Hydrian

in reply to Karl R

@wickedsmoke I know what you mean. I package in Flatpak. More than a few are sloppy about cleaning up their builds.
in reply to Tio

FYI each Flatpak app is like a Git repo and an update just downloads the files that actually changed. The files of all installed apps are stored together in a content-addressable storage, then hardlinked one or more times to form each app.

OSTree-based host OSs like Fedora Atomic work in the same way and hopefully in the future the files will be shared between the host OS and Flatpak apps too.

in reply to Tio

When you install a Flatpak, it will need runtimes (GNOME, KDE, Freedesktop...). These are the ones that really take up disk space. But the good news is that it looks big if you install just one Flatpak application, but the more you install, the more they'll use the same runtimes already installed, and the less disk space they'll occupy.

And no, ungoogled-chromium doesn't require 4-5 GB, just 153 MB...

in reply to Okki

And no, ungoogled-chromium doesn't require 4-5 GB, just 153 MB...

How come on my system it had to download 4-5GB? And yes I use many flatpaks but that didn't seem to help. And this is not the first time am seeing these massive downloads.

in reply to Tio

You can use the flatpak list --columns=name,size command to see the disk space used by all your flatpaks and runtimes.
This entry was edited (6 months ago)
in reply to Okki

And if your package manager doesn't do it automatically, you can also use this command to uninstall old runtimes you no longer need: flatpak uninstall --unused
in reply to Tio

"takes forever to update them even on my 1GB internet connection"? huh?... you're on gigabit internet and it's taking forever? honestly that's not possible... Are you sure you have gigabit internet? or do you mean that your lan port is a gigabit port?..

I use flatpaks and it's really not that big of a deal (plus it happens in the background anyone, so most people will pretty never notice it)

in reply to Thibault Molleman🇧🇪 🌈🐝

Yes I know very well what connection I have but since it has to download around 4-5 GB in that case, it takes a long long time. It depends the server where it is pulling these updates from I guess.... Maybe that particular package is worse than other flatpaks, but I have noticed this issue with long download times and huge download sizes on multiple computers and multiple flatpaks.
in reply to Tio

definitely it's outrageous. it's that way by design. personal example: i don't run KDE but wanted to try okular, and ran the heck away and removed it when i saw it had installed 48,954 files at a cost of 820MB. this is just ridiculous...for a friggin' PDF reader?