Traffic

Traffic measures the volume of data Storyblok sends out, counted in bytes. A single large response consumes more traffic than multiple small ones, so payload size matters as much as request volume.

What counts as traffic

The following outgoing data counts toward a plan’s traffic quota:

• Content Delivery API responses (cached or not).
• Management API responses.
• Asset delivery, including every variation that the Image Service generates (cached or not).
• GraphQL API responses.
• Webhook payloads.

To check a space’s actual consumption, open the space dashboard.

How to reduce traffic

Reducing payload size lowers traffic and improves page performance at the same time:

• Request only the fields you render. Use the stories endpoint’s excluding_fields to omit content fields and excluding_story_fields to omit top-level story properties.
• Request only the stories you need. Fetch relevant stories with filter queries instead of filtering the response in the frontend.
• Serve large static files, such as videos, from your own host, where bandwidth may cost less.
• Follow the caching concept and optimize content fetching. Pass the cv value the API returns instead of a Date.now(). A timestamp bypasses the CDN cache and sends every request to the backend.
• Serve optimized assets with the Image Service. Append /m/ to an image URL to deliver it in WebP format, specify the explicit dimensions, and apply other transformations.

Related resources

Developer Concept: Caching

Technical Limits