The disk space resources available to each customer are also used by the operating system, under which all other relevant software is installed, as well as the images and project files stored by users. During the image upload phase, images are scaled to several different sizes, with the largest ones taking up a megabyte or more, depending on the image format. Project files are files that users can save to a project and that are also included in backups. When making a backup, disk space is also needed to create a zip file. The operating system reserves approximately 4 percent of disk space for its own use so that it can continue to function even when the user has used up the available space on e.g. an 80 GB partition of the SSD device. In the early stages of using the publishing application, the user would have approximately 60 GB available, which is enough to prevent the disk space from running out immediately just for storing images.

If necessary, customers can request an increase in disk space, for which there are two different options, both of which have in common that the disk space cannot be reduced back to its previous size. In the first option, the amount of disk space is increased by choosing a more expensive option from the price list (Hetzner), which may also include more VCPUs and RAM (e.g., 160 GB of disk space cost 15.67 eur/month at the beginning of 2026).

In the second option, disk space is allocated separately so that one can start with e.g. 10 GB and increase it as needed up to 10 terabytes. At the beginning of 2026, the price of this "block storage volume" was 0.55 eur/month for the first 10 GB, 5.52 eur/month for 100 GB, and 565.45 eur/month for 10 TB.

Pricing for block storage volume is hourly, meaning that billing ends when stopping using the disk space. However, since it may contain images and other files, when one wants to stop using it, images and other files need to be moved to the "basic disk" using the publishing application's user interface or, if there is not enough space, delete them. The user settings of the publishing application include a mode that provides information (in a few places on different views) on which disk the images and other files are physically located on, as well as functions for transferring files from one disk to another. These have been designed to be easy to use, so that the user can easily understand what they are doing.

When it was considered that users should have a possibility to to use additional disk space, the Logical Volume Manager (LVM) was thought about as it makes two different disks appear as one to the operating system, but it could fragment different parts of the files across different disks, making it difficult to remove the additional disk later. Thus, a different approach was choosen, and in practice, the additional disk appears to the operating system as a separate directory, which makes it easier to use in a network topology where different components of the publishing application are used on different servers and where the use of a network file system (NFS) is required.