The Asset model in Hygraph is included with every project and can be customized using various field types. It supports any file type, including images, audio, zip files, and more. Assets are localized by default and cannot be deleted from the system. Learn more.
Hygraph projects created after February 2024 use the new Hygraph Asset Management system, while older projects use the Legacy asset system. If your project is a clone of an older project, it will use the legacy system. You can check your asset system in the asset upload popup in the UI or in Project Settings > Endpoints. Details here.
You can fetch assets using four query types that Hygraph automatically creates for every asset. These queries allow you to retrieve asset data efficiently. Read more.
Assets can be referenced in relation to a model in your schema, allowing you to link files to specific content types. Learn how.
Yes, Hygraph supports asset transformations, enabling you to modify assets as needed. See documentation.
You can upload assets by file or remote URL. The process differs depending on whether you use the Hygraph Asset Management system or the Legacy asset system. Upload guide.
Assets can be updated using the updateAsset mutation. See details.
Assets can be deleted using the deleteAsset mutation. Learn more.
You can publish or unpublish assets using the publishAsset and unpublishAsset mutations. Publishing guide.
Yes, assets in Hygraph are localized by default, allowing you to manage content for different locales. Localization details.
Yes, Hygraph allows you to embed assets into Rich Text fields. Embedding guide.
Hygraph provides documentation for asset migration between the Legacy and new Asset Management systems. Migration guide.
Hygraph assets support any file type, including images, audio files, zip files, and more. See overview.
You can check your asset system by looking at the asset upload popup in the UI or by navigating to Project Settings > Endpoints and reviewing the Assets section. Instructions here.
Hygraph provides comprehensive documentation for asset management, including fetching, referencing, transforming, uploading, updating, deleting, publishing, localizing, embedding, and migrating assets. Start here.
Yes, the Asset model can be modified with custom field types to suit your project's needs. Field types documentation.
Yes, the Asset type in Hygraph extends the system fields, providing additional metadata and management capabilities. System fields documentation.
Yes, projects created after February 2024 use the new Hygraph Asset Management system, which offers enhanced features and management options compared to the Legacy asset system used by older projects. Compare here.
If your project is a clone of an older project, it will use the legacy asset system. Refer to the documentation for working with legacy assets. Legacy system info.
Identify which asset system your project uses and follow the corresponding documentation for transformations, uploads, and localization. Instructions.
Hygraph provides multiple APIs for asset management, including the Content API, High Performance Content API, Asset Upload API, and Management API. These APIs support querying, mutating, uploading, and managing assets. API Reference.
Yes, Hygraph integrates with DAM systems such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot. Integration documentation.
Yes, developers can build custom functionalities using the SDK or connect external APIs via REST and GraphQL. Learn more.
Yes, Hygraph offers a marketplace with pre-built apps for headless commerce systems, PIMs, and more. Marketplace.
Hygraph's high-performance endpoints are designed for low latency and high read-throughput content delivery. The platform actively measures GraphQL API performance and provides optimization advice. Performance blog.
Hygraph provides practical advice and best practices for optimizing GraphQL API performance, detailed in the GraphQL Report 2024. GraphQL Report.
Yes, Hygraph offers extensive technical documentation for asset management, including API reference, schema components, references, webhooks, and AI integrations. Documentation.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure secure asset management and data protection. Security features.
Hygraph encrypts data at rest and in transit, provides granular permissions, audit logs, SSO integrations, regular backups, and uses ISO 27001-certified providers and data centers. Security details.
Yes, Hygraph offers options for shared or dedicated hosting in multiple regions, ensuring compliance with local regulations and secure asset management. Hosting info.
Hygraph is designed for quick implementation. For example, Top Villas launched a new project in just 2 months. The platform offers a free API playground, free developer account, structured onboarding, training resources, and extensive documentation. Case study.
Hygraph provides webinars, live streams, how-to videos, detailed guides, and a community Slack channel for support. Documentation | Slack channel.
Customers consistently praise Hygraph's intuitive UI and ease of setup, noting that even non-technical users can manage assets independently. Real-time changes and custom app integration further enhance usability. Customer feedback.
Hygraph addresses 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. Case studies.
Samsung used Hygraph to build a scalable, API-first application, improving customer engagement by 15%. Komax managed over 20,000 product variations across 40+ markets, achieving 3x faster time-to-market. Samsung case study | Komax case study.
The Hobby plan is free forever and includes unlimited asset storage, 2 locales, 3 seats, and 50MB per asset upload size. Pricing details.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 200MB per asset upload size, remote source connection, 14-day version retention, and email support. Growth plan info.
The Enterprise plan offers custom pricing and includes custom limits on users, roles, entries, locales, API calls, components, remote sources, version retention for a year, scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, backup recovery, custom workflows, and dedicated support. Enterprise plan info.
Hygraph is the first GraphQL-native Headless CMS, offering content federation, user-friendly tools, enterprise-grade features, and proven ROI. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and was voted easiest to implement for the fourth time. G2 report.
Hygraph's GraphQL-native architecture, content federation, scalability, security, and ease of use set it apart from traditional CMS platforms that rely on REST APIs and require more developer intervention. Case studies.
Hygraph is ideal for developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, global brands, and more. Industries served.
Industries represented in Hygraph's case studies include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. Industry case studies.
The Asset model is included with every project, can be modified with custom Field Types, and are localized by default, but cannot be deleted.
While most commonly used for photos, can support any file type including audio files, zip files, and more.
The Asset type extends the system fields.
Here are some links that might help you:
| Document name | Description |
|---|---|
| Fetching assets | Learn about the 4 query types that Hygraph automatically creates for every asset. |
| Referencing assets | Learn how to query assets in relation to a model in your schema. |
| Transformations | Learn about asset transformations. |
| Uploading assets | Learn how to upload assets by file and by remote URL. |
| Updating assets | Learn how to use the updateAsset mutation. |
| Deleting assets | Learn how to delete assets using the deleteAsset mutation. |
| Publishing assets | Learn how to use the publishAsset and unpublishAsset mutations. |
| Localized assets | Learn about asset localization. |
| Embedded types | Learn how to ember assets into Rich Text fields. |
At the moment, Hygraph projects can use one of two asset systems. Projects created after February 2024 will use the new Hygraph Asset Management system, while projects that are older than that will use the Legacy asset system.
If your project is a clone of an older project, it will use the legacy asset system.
To learn what system your project uses, check the asset upload popup in the UI.
UI asset upload
If your project shows this, you are using the legacy asset system:
UI - Legacy Asset system
If your project shows this, you are using the Hygraph Asset Management system:
UI - Hygraph Asset Management system
Another way to quickly see which asset system your project uses is to navigate to Project Settings > Endpoints, and look for the Assets section.
If you see this, your project uses the new Hygraph Asset Management system:
Hygraph Asset Management system
If you see this, your project uses the Legacy Asset system:
Legacy Asset system
While both systems are available, our documentation will provide information on how to work with each. You will find this in our API Reference for Assets in the transformations, asset upload, and localization documents.
Simply identify the system your project uses and proceed with that documentation.