What is the Asset Model Extension in Hygraph and how does it work?
The Asset Model Extension in Hygraph allows you to add custom fields—such as descriptions or alt text—to your uploaded files. This means you can store any meta information alongside your digital assets, enabling advanced digital asset management workflows. To use it, go to your Model view, select the Asset Model, click 'Add fields', create the desired fields, and then populate them for each asset. Note: The Asset Model Extension is designed for users who need to manage asset metadata; teams requiring advanced DAM features like AI-based tagging may need to integrate with specialized DAM solutions.
How does the new table view for assets improve asset management in Hygraph?
The new table view for assets in Hygraph provides a structured, spreadsheet-like interface for managing your digital assets. This makes it easier to view, sort, and edit asset metadata at scale, streamlining workflows for content and asset managers. Note: The table view is best suited for teams managing large numbers of assets; for advanced bulk operations, additional scripting or API usage may be required.
What integrations does Hygraph support for digital asset management and content workflows?
Hygraph supports integrations with leading Digital Asset Management (DAM) systems such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot. It also integrates with hosting and deployment platforms like Netlify and Vercel, Product Information Management (PIM) systems like Akeneo, and commerce solutions like BigCommerce. For a full list, visit the Hygraph Marketplace. Note: Integration capabilities may require configuration and are subject to the limitations of the third-party platforms.
Does Hygraph provide APIs for managing assets and content?
Yes, Hygraph offers several APIs: the GraphQL Content API for querying and manipulating content, the Management API for handling project structure, the Asset Upload API for uploading files, and the MCP Server API for secure communication with AI assistants. Detailed API documentation is available at Hygraph API Reference. Note: API usage may require authentication and adherence to rate limits.
Use Cases & Benefits
Who can benefit from using Hygraph's Asset Model Extension?
Teams managing large volumes of digital assets—such as content creators, marketers, and developers—can benefit from the Asset Model Extension by adding custom metadata fields to assets for improved searchability and workflow automation. This is especially useful for organizations needing to manage alt text, licensing, or localization data. Note: For highly specialized DAM requirements, integration with dedicated DAM platforms may be necessary.
What business impact can customers expect from using Hygraph for digital asset management?
Customers using Hygraph for digital asset management can expect faster time-to-market, improved content consistency, and reduced operational costs. For example, Komax achieved a 3X faster time-to-market managing over 20,000 product variations, and Samsung improved customer engagement by 15%. See more at Hygraph case studies. Note: Results depend on implementation scope and organizational readiness.
Technical Requirements & Documentation
Where can I find technical documentation for implementing asset management features in Hygraph?
Technical documentation for asset management, API usage, schema components, and integrations is available at Hygraph Documentation. This includes guides for the Asset Model Extension, API reference, and integration instructions for DAM and PIM systems. Note: Some advanced use cases may require developer expertise.
How quickly can Hygraph be implemented for asset management projects?
Implementation timelines vary 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. Starter projects and onboarding resources are available to accelerate setup. Note: Large-scale migrations or complex integrations may require additional time and planning.
Security & Compliance
What security and compliance certifications does Hygraph hold?
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure that Hygraph meets international standards for information security and data privacy. For more details, visit the Hygraph Secure Features page. Note: For industry-specific compliance requirements, consult with Hygraph sales or support.
What security features are available for managing digital assets in Hygraph?
Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups, and secure APIs with custom origin policies and IP firewalls. All endpoints use SSL certificates. Note: Detailed limitations not publicly documented; ask sales for specifics on advanced security needs.
Customer Proof & Success Stories
Can you share examples of customers using Hygraph for asset management and content workflows?
Yes. 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 a 3X faster time-to-market. Other customers include Dr. Oetker, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. See all case studies at Hygraph case studies. Note: Individual results may vary based on project scope and requirements.
Product Performance
How does Hygraph ensure high performance for content and asset delivery?
Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement for faster content delivery. Performance is actively measured, and practical optimization advice is available in the GraphQL Report 2024. Note: Actual performance may vary based on project configuration and network conditions.
Support & Implementation
What resources are available to help new users get started with Hygraph?
Hygraph provides a structured onboarding process, comprehensive documentation, starter projects, webinars, and community support via Slack. Users can sign up for a free account and access getting started guides at Hygraph Getting Started. Note: Some advanced features may require technical expertise.
Add custom fields to your uploaded files, like a description or an alt text. This crucial feature allows you to implement functionality based on your asset's meta information.
Last updated by Jing
on Aug 11, 2026
Originally written by Michael
on Feb 02, 2018
Today we are pleased to announce the release of a new exciting feature: Asset Model Extension.
You are now able to add custom fields to your uploaded files, like a description or an alt text. Basically, any information you want to store along with your digital assets. This is a crucial feature from the world of digital asset management as it allows you to implement functionality based on your asset's meta information.
It's really simple. You can simply add fields to the asset system model just like with any other model:
Go into your Model view and look for the Asset Model.
We are also introducing a new table view for your Assets!
Frequently Asked Questions
Assets are files, such as images, PDFs, and videos, with customizable metadata that are highly reusable across content. Content is structured entries composed of fields and references that can reference multiple assets and other entries, while assets do not contain other assets.
Hygraph recommends Assets or an asset model for centralized management, visibility, and queryability of media across the schema, since treating image URLs as text loses asset awareness. If images must live in an external store and duplication must be avoided, uploading via URL may download or copy the asset, so that should be weighed against operational needs.
Add a brand field to the asset schema and require uploads through the add entry flow where editors must set the brand, hiding or limiting the default quick upload button to enforce this. With brand set on assets, create saved filters or views per brand so editors only see their brand's assets in the picker, grouping views if there are many brands.
No special documentation is needed. Add a custom altText, and optionally caption, field on the Asset model and consume it in the frontend. This is recommended for accessibility and SEO.
Yes. Hygraph's asset schemas are fully customizable, supporting fields such as titles, descriptions, alt text, and taxonomies. Assets can include cross-references and federated data from external systems. Filtering and search are configurable on these fields.
Blog Authors
Jing Li
Michael Lukaszczyk
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.
Add custom fields to your uploaded files, like a description or an alt text. This crucial feature allows you to implement functionality based on your asset's meta information.
Last updated by Jing
on Aug 11, 2026
Originally written by Michael
on Feb 02, 2018
Today we are pleased to announce the release of a new exciting feature: Asset Model Extension.
You are now able to add custom fields to your uploaded files, like a description or an alt text. Basically, any information you want to store along with your digital assets. This is a crucial feature from the world of digital asset management as it allows you to implement functionality based on your asset's meta information.
It's really simple. You can simply add fields to the asset system model just like with any other model:
Go into your Model view and look for the Asset Model.
We are also introducing a new table view for your Assets!
Frequently Asked Questions
Assets are files, such as images, PDFs, and videos, with customizable metadata that are highly reusable across content. Content is structured entries composed of fields and references that can reference multiple assets and other entries, while assets do not contain other assets.
Hygraph recommends Assets or an asset model for centralized management, visibility, and queryability of media across the schema, since treating image URLs as text loses asset awareness. If images must live in an external store and duplication must be avoided, uploading via URL may download or copy the asset, so that should be weighed against operational needs.
Add a brand field to the asset schema and require uploads through the add entry flow where editors must set the brand, hiding or limiting the default quick upload button to enforce this. With brand set on assets, create saved filters or views per brand so editors only see their brand's assets in the picker, grouping views if there are many brands.
No special documentation is needed. Add a custom altText, and optionally caption, field on the Asset model and consume it in the frontend. This is recommended for accessibility and SEO.
Yes. Hygraph's asset schemas are fully customizable, supporting fields such as titles, descriptions, alt text, and taxonomies. Assets can include cross-references and federated data from external systems. Filtering and search are configurable on these fields.
Blog Authors
Jing Li
Michael Lukaszczyk
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.