Storage Usage and Limits
View how much storage your workspace has consumed and understand what counts toward your usage.
What it is
ConnectWyze tracks storage usage per workspace in bytes and object count. The usage figures reflect the total size of files your workspace has written to its configured storage provider — whether that is the default Cloudflare R2 or a custom provider you configured.
Usage is tracked fire-and-forget: the upload response is not delayed by the tracking call.
When you'd use it
- You want to understand how much storage your generated images and assets are consuming.
- You are evaluating whether to switch to a custom storage provider for cost reasons.
- You notice usage growing unexpectedly and want to investigate.
Quick start (user)
View your workspace's storage usage
Go to Settings → Usage (/dashboard/settings/usage). The page shows:
- Total bytes stored
- Total object count
Settings reference
What counts toward usage
| Item | Counted? | Notes |
|---|---|---|
| Generated images | Yes | Each image upload increments usage by its file size |
| Feed media (mirrored images) | Yes | Images mirrored from data-source URLs to workspace storage |
| Template thumbnails | Yes | Small thumbnails generated when you save a template |
| Custom fonts | Yes | Font files uploaded to the workspace |
| Deleted files | No | Deletion decrements the byte count |
Byte tracking behavior
- Upload:
bytesStoredandobjectCountincrement when a file is written to storage. - Deletion:
bytesStoreddecrements by the size of the deleted file. The counter usesGREATEST(0, current − size)— it will not go below zero even if tracking state drifts. - Provider changes: Usage is tracked at the ConnectWyze layer regardless of which underlying provider is active. If you switch providers, historical uploads to the old provider are not re-scanned — the counter reflects cumulative uploads since you started using ConnectWyze.
Regeneration behavior
When a workflow re-renders an image, ConnectWyze uploads the new file before deleting the old one (upload-first-delete-last). For content-addressed paths (workflows), if the generated content is identical the file overwrites in place and usage stays the same. If the content changed, the old file is deleted and usage reflects the new file size.
Troubleshooting
| Symptom | Fix |
|---|---|
| Usage shows 0 even after generating images | The usage page may take a short time to reflect recent uploads. Reload the page. If usage remains 0, verify your workspace has generated at least one image and that the storage configuration is active. |
| Usage is higher than expected | Workflow runs with many items each write a file per generated image per artboard. Multiple artboard sizes on a single template multiply the image count. |
| Usage did not decrease after deleting images | Deletion tracking is fire-and-forget. If the delete call failed (e.g. the object was already missing from storage), the counter may not have decremented. This is cosmetic — the underlying storage is not affected. Contact support if the discrepancy is large. |
| Object count and byte count are out of sync | This can occur if files were deleted directly in your cloud console rather than through ConnectWyze. The tracking counters are not authoritative — they are approximations for display purposes. |