Why media and storage become the bottleneck

ConcreteCMS version 9 (and the 7/8 line before it) manages images through a thumbnailing system that behaves very differently from a simple upload folder. Every image dropped into the File Manager is stored under /application/files/, and for each thumbnail type defined in the dashboard the system generates additional resized versions, each with a normal-DPI and a doubled (Retina) variant. The default Elemental theme alone installs three thumbnail types — Small, Medium, and Large — so a single uploaded photo can quietly produce six or more derivative files the moment it is saved.

On managed shared hosting this multiplication matters for two reasons that are easy to overlook. The first is inode count: every generated thumbnail is a separate file, and CloudLinux accounts enforce inode limits alongside disk-space quotas. A gallery-heavy site with thousands of originals can hit the inode ceiling long before it runs out of actual gigabytes, which then blocks new uploads, cache writes, and even email. The second is CPU: when a thumbnail is missing, ConcreteCMS regenerates it through PHP using the Imagine library, and a burst of uncached requests to large images can spike your LiteSpeed PHP workers. Because you are operating as an unprivileged hosting user, the levers you control are the dashboard settings, the File Manager, your .htaccess and .user.ini files, and the account's local error_log — not server configuration. Those tools are enough to shape thumbnail generation, compression, delivery, and storage, as long as you use them deliberately.

Before changing anything, get a sense of scale. In cPanel, open File Manager and browse to public_html/application/files/ (or your document-root equivalent). The cache/ subdirectory holds generated thumbnails and can be safely cleared; ConcreteCMS will rebuild entries on demand. In DirectAdmin, the same path is reachable through the file manager under your domain's document root. Check your account's inode usage in the cPanel Statistics sidebar or DirectAdmin's usage panel so you have a baseline before and after optimization.

Controlling thumbnail types and compression from the dashboard

The single most effective change for most sites is reducing the number of thumbnail types and trimming their dimensions. Log in and go to Dashboard > System & Settings > Files > Thumbnails (the direct path is /dashboard/system/files/thumbnails). You will see each defined type with its maximum width, height, and sizing mode. Types marked as required cannot be deleted, but the theme-created ones usually can. If your layout never actually references the Large type, removing it stops ConcreteCMS from generating two extra derivatives for every future upload.

For the types you keep, confirm the sizing mode. Proportional sets a maximum width or height without cropping, which keeps aspect ratios intact and avoids wasted pixels; exact crops to a fixed box. Set widths to the real display size in your theme — a content image rarely needs to exceed 1140 px. One important caution: thumbnail types are applied at upload or rescan time, so changing a type does not retroactively shrink existing derivatives. After editing types, select images in the File Manager and use the Rescan action to regenerate versions against the new definitions, then clear the old cache folder.

Compression quality lives under Dashboard > System & Settings > Files > Optimization (/dashboard/system/files/image_optimization area) and in the thumbnail options screen. ConcreteCMS exposes a default JPEG compression value; dropping it from the default toward roughly 75–82 typically removes 20–40% of file weight with no visible artifacts on photographic content. If you manage an application/config/concrete.php file through the File Manager, the same control exists as a configuration key so you can set it once for the whole site:

<?php
return [
    'misc' => [
        'default_jpeg_image_compression' => 80,
        'default_png_image_compression'  => 8,
    ],
];

Keep the master originals as clean as possible before they ever reach the server. Running photos through a desktop tool such as Squoosh or ImageOptim to pre-size and compress them means ConcreteCMS starts from a smaller source, which lowers both the stored original and every derivative generated from it. This habit does more for inode and disk pressure than any single server tweak, because it reduces the raw material the thumbnailer has to work with.

WebP/AVIF delivery and browser caching

ConcreteCMS core does not transparently convert uploads to WebP or AVIF on its own; that behavior comes from a marketplace add-on. If you install one such as the Afixia Automatic WebP conversion package through Dashboard > Extend Concrete CMS, its controls appear under System & Settings > Optimization > WebP Settings. From there you enable browser autodetection so JPG and PNG images are served as WebP when the visitor's browser advertises support, set a quality value, and optionally let the add-on manage an Apache/LiteSpeed rewrite rule. Whether conversion actually succeeds depends on the PHP build your account runs. Open the cPanel Select PHP Version (or DirectAdmin's PHP Selector) and confirm that the gd extension — or ImageMagick — includes WebP support; without it, the add-on falls back to serving originals. AVIF support is far less consistent on shared PHP builds, so treat WebP as the dependable target and AVIF as a bonus only if your selected PHP version advertises it.

Regardless of format, browser caching is something you own directly through .htaccess in your document root. LiteSpeed honors standard Apache cache directives, so add long expirations for static media so returning visitors re-use local copies instead of re-requesting them:

<IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType image/jpeg "access plus 1 year"
    ExpiresByType image/png  "access plus 1 year"
    ExpiresByType image/gif  "access plus 1 year"
    ExpiresByType image/webp "access plus 1 year"
    ExpiresByType image/avif "access plus 1 year"
    ExpiresByType image/svg+xml "access plus 1 year"
</IfModule>
<IfModule mod_headers.c>
    <FilesMatch "\.(jpe?g|png|gif|webp|avif|svg)$">
        Header set Cache-Control "public, max-age=31536000, immutable"
        Header append Vary Accept
    </FilesMatch>
</IfModule>

The Vary: Accept header is important whenever a WebP add-on serves different bytes to different browsers from the same URL, since it tells any CDN or proxy to cache the variants separately. If you route the site through a CDN, point it at your canonical domain and let it pull and cache the already-optimized derivatives; the cache headers above make that behavior predictable without any origin-side configuration you cannot reach.

Upload limits, alternate storage, and S3 offloading

Large originals frequently fail to upload not because of ConcreteCMS but because of PHP limits. As an unprivileged user you can raise these per-account with a .user.ini file placed in your document root, which LiteSpeed and the CloudLinux PHP selector both read:

upload_max_filesize = 64M
post_max_size = 72M
memory_limit = 256M
max_execution_time = 180
max_input_time = 180

Keep post_max_size slightly above upload_max_filesize, and give memory_limit enough headroom, since the Imagine library loads full images into memory while generating thumbnails — an oversized source can exhaust a small limit mid-resize and leave a partial derivative. If uploads still fail, check the local error_log in the same directory; messages mentioning allowed memory size or exceeded execution time point straight back to these values. Changes can take a minute to apply because of PHP process caching.

For storage pressure itself, ConcreteCMS lets you define additional file storage locations at Dashboard > System & Settings > Files > File Storage Locations. The built-in option is an Alternate local directory: you supply a root path and, if you set a relative path, files are served directly by the web server. Leave the relative path blank and every file request is routed through PHP as /download_file/<id>/<id>, which enforces permissions but increases CPU — a trade-off worth understanding before you rely on it for public images. Any configured location can be set as the default for new uploads, and existing files can be moved individually through each file's Permissions & Access dialog.

To move media off your account entirely, install an S3-compatible storage add-on (the marketplace and open-source packages support Amazon S3 and S3-compatible providers such as DigitalOcean Spaces). Once installed, a new storage type appears in the same Storage Locations screen, where you enter the bucket, credentials, and an optional public or CloudFront/CDN base URL that is used to build file URLs. Setting that offloaded location as the default means future uploads and their thumbnails live on object storage, which directly relieves both your disk quota and the inode count that so often caps shared-hosting accounts. Treat credentials as scoped and private, grant only the bucket access the site needs, and verify delivery on a few test files before migrating existing media in bulk. For a deeper look at how inode and worker ceilings behave on this platform, see our guide on diagnosing CPU, RAM, PHP worker, and inode bottlenecks on shared hosting.