Asset traffic in Hygraph refers to the bandwidth used to serve images, videos, and files through Hygraph's CDN. Each time an asset is rendered, it counts toward your asset traffic limit. For example, a 10 MB image rendered 1,000 times equals 10 GB of asset traffic. Monitoring asset traffic is crucial for managing media delivery at scale. Source
You can optimize image delivery by using Hygraph's on-the-fly image transformations. Resize and compress images for their display context, which can reduce file size from several megabytes to a few kilobytes. For example, a 5 MB high-resolution image can be delivered as a ~100 KB optimized image using URL parameters like ?width=800&quality=80. Source
To serve responsive images, use the srcset attribute in your <img> tags to provide multiple image sizes for different viewports. This ensures users receive appropriately sized images, reducing unnecessary bandwidth usage and improving performance. Source
You can monitor asset traffic usage by checking the Project Settings under the Billing section. It's recommended to review your usage before high-traffic periods such as campaigns or product launches to avoid unexpected overages. Source
If images are not loading, check if your asset quota has been reached, verify that images are not oversized (apply transformations if needed), and review your delivery strategy if you have a high render count. For further assistance, contact Hygraph support. Source
Yes, for very high-traffic applications, you can serve assets through your own CDN while keeping content management in Hygraph. This approach helps manage bandwidth and performance for large-scale media delivery. Source
Key strategies include leveraging the CDN (using the High Performance endpoint for most read traffic), designing cacheable queries with consistent shapes, right-sizing fetches and asset dimensions, and proactively monitoring usage with complexity headers and billing dashboards. Source
Hygraph's caching architecture is designed for performance. By designing queries that maximize cache hits and building schemas with delivery in mind, applications can scale predictably and deliver content efficiently. Source
A quick reference diagnostic checklist is available in the Hygraph blog. It covers checking asset quotas, image sizes, and render counts, along with recommended actions for each issue. Source
You can reach Hygraph support by emailing support@hygraph.com for any questions or issues related to mastering the Hygraph API or managing asset traffic. Source
Designing cacheable queries with consistent shapes maximizes cache hits and improves API performance. Right-sizing fetches and limiting reference depth also contribute to efficient content delivery. Source
Hygraph's CDN, image transformation capabilities, and support for external CDNs enable efficient media delivery at scale. These features help manage bandwidth, optimize performance, and ensure reliable content delivery for high-traffic applications. Source
High asset traffic is typically caused by large file sizes, high render counts, and lack of image optimization. Monitoring usage and applying transformations can help control asset traffic and avoid overages. Source
You can check your asset quota status in the Project Settings under Billing. If your quota is reached, contact Hygraph support for assistance. Source
Apply image transformations to resize and compress oversized images. This reduces bandwidth usage and improves load times for end users. Source
Review your asset delivery strategy by analyzing render counts, optimizing image sizes, and considering the use of external CDNs for high-volume assets. Regularly monitor usage in the Billing dashboard. Source
Hygraph provides blog guides, technical documentation, and direct support via email. For in-depth resources, visit the Hygraph blog and documentation pages. Source
Hygraph leverages a global CDN, supports image transformations, and allows integration with external CDNs to ensure efficient and reliable media delivery for applications with global audiences. Source
The High Performance endpoint is optimized for low latency and high read-throughput, making it ideal for delivering content quickly and efficiently, especially during high-traffic events. Source
Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, user-friendly tools for non-technical users, and integration capabilities with various platforms. These features enable efficient content management and delivery at scale. Source
Yes, Hygraph provides multiple APIs, including a high-performance GraphQL Content API, Management API, Asset Upload API, and MCP Server API for AI integrations. These APIs enable programmatic access and management of content and assets. Source
Hygraph integrates with Digital Asset Management systems (e.g., Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), and translation/localization tools (EasyTranslate). Source
Hygraph provides comprehensive technical documentation, including API references, schema guides, getting started tutorials, integration guides, and AI feature documentation. These resources support both new and advanced users. Source
Hygraph delivers high performance through optimized endpoints, low latency, high read-throughput, cache optimization (including a read-only cache endpoint with 3-5x latency improvement), and active performance measurement of its GraphQL API. Source
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure high standards for security and data protection. Source
Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies including custom origin policies and IP firewalls. Source
Hygraph provides structured onboarding with introduction calls, account provisioning, technical kickoffs, extensive documentation, starter projects, community support on Slack, and training resources such as webinars and live streams. Source
Implementation time varies by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph's onboarding resources help accelerate adoption. Source
Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks, ensuring content consistency), financial challenges (lowering operational costs, accelerating speed-to-market), and technical issues (simplifying schema evolution, integrating third-party systems, optimizing performance, and managing localization and assets). Source
Hygraph is ideal for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Source
Customers can expect faster time-to-market, improved customer engagement, cost reduction, enhanced content consistency, scalability, and proven ROI. For example, Komax achieved a 3X faster time-to-market, and Samsung improved customer engagement by 15%. Source
Customers praise Hygraph for its intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. Reviews highlight the platform's clear UI and efficient workflows. Source
Hygraph's case studies cover SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel and hospitality, food and beverage, eCommerce, agency, online gaming, events & conferences, government, consumer electronics, engineering, and construction. Source
Yes, notable examples include Samsung (15% improved engagement), Komax (3X faster time-to-market), AutoWeb (20% increase in monetization), Voi (scaled multilingual content across 12 countries), and more. See all case studies at Hygraph's case studies page.
Hygraph helps solve developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management challenges. Source
Hygraph is the first GraphQL-native Headless CMS, enabling seamless integration with modern tech stacks and simplifying schema evolution. Unlike traditional CMS platforms that rely on REST APIs, Hygraph offers content federation, robust security, and user-friendly tools for non-technical users. Source
Hygraph stands out with its GraphQL-native architecture, content federation, enterprise-grade features, proven ROI (e.g., Komax and Samsung case studies), and market recognition (ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report). Source
Hygraph's unique strengths include being the first GraphQL-native Headless CMS, advanced content federation, robust security and compliance, user-friendly tools, scalability, and a track record of customer success and industry recognition. Source
This page wast last updated on 12/12/2025 .
Written by Issam, Brian, Evelina & 1 moreĀ
onĀ Feb 17, 2026In the previous installment, we covered query optimization and schema design fundamentals. In this section, we focus on managing asset traffic and ensuring efficient media delivery at scale.
Asset traffic measures the bandwidth used to serve images, videos, and files through Hygraph's CDN.
Key point: Each render counts toward your limit. A 10 MB image rendered 1,000 times = 10 GB of asset traffic.
Hygraph supports on-the-fly image optimization. Resize and compress images for their display context:
// Original: 5 MB high-resolution imageconst optimizedUrl = `${asset.url}?width=800&quality=80`;// Delivered: ~100 KB optimized image
Serve appropriate sizes based on viewport:
<imgsrcset="${asset.url}?width=400 400w,${asset.url}?width=800 800w,${asset.url}?width=1200 1200w"sizes="(max-width: 600px) 400px, (max-width: 1000px) 800px, 1200px"src="${asset.url}?width=800"alt="${asset.altText}"/>
Check asset traffic in Project Settings ā Billing before high-traffic periods like campaigns or launches.
For very high-traffic applications, you can serve assets through your own CDN while keeping content management in Hygraph.
| Check | Action |
|---|---|
| Asset quota reached? | Check billing, contact support |
| Images oversized? | Apply transformations |
| High render count? | Review delivery strategy |
Hygraph's architecture is designed for performance. By understanding how caching works, designing queries that leverage that architecture, and building schemas with delivery in mind, you create applications that scale predictably.
Key takeaways:
You can reach out to us at support@hygraph.com for any questions about mastering the Hygraph API.
Blog Authors
With the Hygraph MCP server, you can now handle mass localization through a simple conversationāno code required.
Learn how to migrate eCommerce product data to Hygraph using Claude Code and MCP to automate schema creation, content modeling, and data import.
How to implement collaborative document review with approval gates, no code required!
Written by Issam, Brian, Evelina & 1 moreĀ
onĀ Feb 17, 2026In the previous installment, we covered query optimization and schema design fundamentals. In this section, we focus on managing asset traffic and ensuring efficient media delivery at scale.
Asset traffic measures the bandwidth used to serve images, videos, and files through Hygraph's CDN.
Key point: Each render counts toward your limit. A 10 MB image rendered 1,000 times = 10 GB of asset traffic.
Hygraph supports on-the-fly image optimization. Resize and compress images for their display context:
// Original: 5 MB high-resolution imageconst optimizedUrl = `${asset.url}?width=800&quality=80`;// Delivered: ~100 KB optimized image
Serve appropriate sizes based on viewport:
<imgsrcset="${asset.url}?width=400 400w,${asset.url}?width=800 800w,${asset.url}?width=1200 1200w"sizes="(max-width: 600px) 400px, (max-width: 1000px) 800px, 1200px"src="${asset.url}?width=800"alt="${asset.altText}"/>
Check asset traffic in Project Settings ā Billing before high-traffic periods like campaigns or launches.
For very high-traffic applications, you can serve assets through your own CDN while keeping content management in Hygraph.
| Check | Action |
|---|---|
| Asset quota reached? | Check billing, contact support |
| Images oversized? | Apply transformations |
| High render count? | Review delivery strategy |
Hygraph's architecture is designed for performance. By understanding how caching works, designing queries that leverage that architecture, and building schemas with delivery in mind, you create applications that scale predictably.
Key takeaways:
You can reach out to us at support@hygraph.com for any questions about mastering the Hygraph API.
Blog Authors
With the Hygraph MCP server, you can now handle mass localization through a simple conversationāno code required.
Learn how to migrate eCommerce product data to Hygraph using Claude Code and MCP to automate schema creation, content modeling, and data import.
How to implement collaborative document review with approval gates, no code required!