Understanding customer storage composition and usage breakdown on WoodWing Cloud

Customer storage on WoodWing Cloud is made up of several distinct categories of files that support both content preservation and day-to-day usability of the platform. While native object files are the most visible component, a significant portion of storage is consumed by historical versions and system-generated preview assets.

Below is a high-level breakdown of the major contributors to total storage usage on WoodWing Cloud. These categories are applicable to both Studio and Assets.

Current object versions

This category includes:

• The latest version of each object
• Original, native renditions (such as layouts, images, and articles)

These files represent the active content currently in use and typically account for a relatively small portion of total storage.

Older object versions

Historical versions of objects are retained to support:

• Version history
• Restoring a previous version

For customers with frequent updates, especially to layouts, older versions accumulate quickly and form a substantial share of total storage.

Preview files for layouts

To enable visual workflows, the system generates preview images for layouts.

Key characteristics:

• Each layout version has its own preview
• Preview files are significantly larger than thumbnails
• Previews are retained for both current and older layout versions

Because layouts often have many historical versions, they can be a large driver of storage usage, particularly for long-running or highly iterative environments.

Page previews and thumbnails

Additional storage is consumed by:

• Page previews
• Thumbnail images
• Other derived visual assets

Individually, these files are small, but at scale, across many pages and versions, they contribute to overall storage consumption.

Key takeaway

Customer storage is not driven solely by active content. The majority of space is consumed by historical object versions and the preview assets generated for usability, especially for layouts with many revisions.

This storage profile is expected behavior and scales naturally with:

• The number of layout versions
• Frequency of content updates
• Retention of historical versions over time