The Asset model is included with every Hygraph project by default. It can be modified with custom field types and is localized by default, but it cannot be deleted. While most commonly used for photos, the Asset model supports any file type, including audio files, zip files, and more. Note: The Asset model cannot be removed from a project.
Hygraph projects use either the new Hygraph Asset Management system (for projects created after February 2024) or the Legacy asset system (for older projects or clones of older projects). To check which system your project uses, open the asset upload popup in the UI or navigate to Project Settings > Endpoints and look for the Assets section. The UI will display either the Hygraph Asset Management system or the Legacy Asset system. Note: Documentation for both systems is available, but features may differ between them.
The Assets API in Hygraph allows you to fetch, reference, transform, upload, update, delete, publish, unpublish, and localize assets. Each operation is documented in detail, with guides available for fetching assets, referencing assets, transformations, uploading assets, updating assets, deleting assets, publishing/unpublishing assets, localization, and embedding assets in Rich Text fields. Note: Some operations may differ between the Hygraph Asset Management system and the Legacy asset system.
To upload assets in Hygraph, use the asset upload popup in the UI or the Asset Upload API. Projects created after February 2024 use the Hygraph Asset Management system, while older projects use the Legacy asset system. The upload process and available features may differ between these systems. For detailed instructions, refer to the Uploading Assets documentation. Note: If your project is a clone of an older project, it will use the legacy asset system.
Assets in Hygraph are localized by default, allowing you to manage and deliver content in multiple languages or regions. For more information, see the Localized Assets documentation. Note: Localization features may vary between the Hygraph Asset Management system and the Legacy asset system.
Yes, you can embed assets into Rich Text fields in Hygraph. This allows for more flexible content structures and richer digital experiences. For implementation details, refer to the Embedded Types documentation. Note: Embedding capabilities may differ between asset systems.
Comprehensive technical documentation for the Assets API and related features is available at Assets API Reference. This includes guides on fetching, referencing, transforming, uploading, updating, deleting, publishing, localizing, and embedding assets. Additional resources are available for schema components, permissions, caching, and webhooks. Note: Always consult the documentation specific to your asset system (Hygraph Asset Management or Legacy).
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. All endpoints, including those for asset management, use SSL certificates for secure connections. Data is encrypted in transit and at rest. Note: For more details, visit the Secure Features page.
Hygraph's high-performance endpoints are optimized for low latency and high read-throughput content delivery. A read-only cache endpoint provides 3-5x latency improvement, ensuring faster asset delivery. Performance is actively measured, and practical advice for developers is available in the GraphQL Report 2024. Note: Performance may vary depending on project configuration and asset system.
Hygraph offers integrations with several Digital Asset Management (DAM) platforms, including Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot. Additional integrations are available for hosting (Netlify, Vercel), PIM (Akeneo), and translation/localization (EasyTranslate). For a complete list, visit the Hygraph Marketplace. Note: Integration availability may depend on your asset system and project configuration.
The Asset model cannot be deleted from a project. Projects cloned from older projects will use the Legacy asset system, which may lack features available in the new Hygraph Asset Management system. Some operations and integrations may differ between the two systems. Detailed limitations are not publicly documented; ask sales or support for specifics regarding your use case.
This page wast last updated on 12/12/2025 .
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.
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.