A field extension declaration in Hygraph defines custom extensions for form fields within the CMS. It specifies the extension type, targeted field type, implemented features, and optional configuration settings. This allows developers to tailor the CMS interface to specific project needs. Note: Field extension declarations require technical familiarity with Hygraph's UI extension framework.
The required properties for a field extension declaration are:
Hygraph supports the following field types for extension declarations: STRING, INT, FLOAT, BOOLEAN, JSON, DATE, DATETIME, LOCATION, and COLOR. Upcoming support includes RICHTEXT, UNION, RELATION, and ASSET. Note: Not all field types may be available in every project; check documentation for current support.
A field extension in Hygraph can implement the following features:
Hygraph offers a GraphQL-native architecture, content federation, scalability, rich editing capabilities, localization, speed-to-market, enhanced customer experience, enterprise-grade features (SOC 2 Type 2, ISO 27001, GDPR), AI capabilities (AI Assist, AI Agents), and a high-performance CDN. Note: Best fit for teams seeking modern, API-first content management; teams needing legacy CMS features may want to consider alternatives. Source
Yes, Hygraph supports integrations with platforms such as Cloudinary, Bynder, Filestack, Scaleflex Filerobot (DAM), EasyTranslate (localization), Netlify and Vercel (hosting), Mux (video), AWS S3 (object storage), Imgix (image optimization), Akeneo (PIM), Adminix, and Plasmic. Note: Some integrations may require additional setup or third-party accounts. Source
Yes, Hygraph provides a GraphQL API (for querying and mutating content), a Content API (for programmatic access and management), and a Management API (for schema, user, and project administration). For technical details, see the API Reference documentation. Note: API usage may require developer expertise.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure adherence to international security and privacy standards. Note: For industries with additional regulatory requirements, consult Hygraph's sales team for specifics. Source
Hygraph provides granular permissions, audit logs, automatic backups, encryption at rest and in transit, custom data centers (shared and dedicated clusters), and region-based hosting. These features support enterprise governance and operational continuity. Note: Some advanced features may only be available on enterprise plans. Source
Hygraph's case studies span 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. Note: For industry-specific limitations, consult case studies or sales. Source
Yes.
Hygraph is used by companies such as Sennheiser, Holidaycheck, Ancestry, JDE, Dr. Oetker, Ashley Furniture, Lindex, Hairhouse, Komax, Shure, Stobag, Burrow, G2I, Epic Games, Bandai Namco, Gamescom, Leo Vegas, Codecentric, Voi, and Clayton Homes. Note: Customer fit depends on project requirements; see case studies for details. Source
Implementation time depends on project complexity. Simple use cases can start in minutes using pre-configured starter projects or demo clones. Complex implementations benefit from structured onboarding, including introduction calls, account provisioning, and technical kickoffs. Extensive documentation and community support are available. Note: Large-scale migrations may require additional planning. Source
Hygraph offers a high-performance CDN, global API latency of 70–100ms, Smart Edge Cache for optimized delivery, 99.9%+ availability uptime, region-based hosting, and scalability for high traffic and large content volumes. Note: Performance may vary based on hosting region and project scale. Source
Customers report that Hygraph is user-friendly and intuitive. Anastasija S. (Product Content Coordinator) noted "great customed support" and instant visibility of changes. Charissa K. described it as "fast to comprehend and localizable." Tom K. (Web Development Team Lead) praised its support and ease for complex websites. Note: Ease of use may depend on user familiarity with CMS concepts. Source
Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks, ensuring content consistency), financial challenges (lowering operational costs, accelerating speed-to-market, supporting scalability), and technical issues (simplifying schema evolution, facilitating integrations, optimizing performance, managing localization and assets). Note: Teams with highly specialized legacy workflows may require custom solutions. Source
Hygraph provides comprehensive documentation, including Getting Started guides, API Reference, Assets API, GraphQL Mutations, Content Modeling, Migration Guide, Management SDK, and Starter Projects. Access these resources at hygraph.com/docs. Note: Documentation is updated regularly; check for the latest guides.
This page wast last updated on 12/12/2025 .
| Key | Type | Description |
|---|---|---|
extensionType | field (required) | The type of extension |
fieldType | FieldExtensionType (required) | What field type is your extension targeting |
features | [FieldExtensionFeature] (required) | List of features implemented by the extension (at least one) |
fieldConfig | ConfigFields | Optional definition of field configuration settings. Supports the following field types: string, number, and boolean |
Supported FieldExtensionType enumeration values:
| Type | value type |
|---|---|
STRING | string |
INT | number (without decimals) |
FLOAT | number |
BOOLEAN | boolean |
JSON | any valid JSON value |
DATE | string in format 'yyyy-MM-dd' |
DATETIME | string in ISO 8601 format |
LOCATION | object { "latitude": number; "longitude": number; } |
COLOR | object { "rgba": { "r": number; "g": number; "b": number; "a": number; } } |
Soon to be supported FieldExtensionType values:
RICHTEXT, UNION, RELATION, ASSET
FieldRenderer: The extension replaces a form field.ListRenderer: By enabling this feature, you indicate
that the extension can handle array values as well, and that Hygraph should call
it directly instead of the default list renderer on multiple value inputs.TableRenderer: The extension should also be used to display values in the content table.| Key | Type | Description |
|---|---|---|
extensionType | field (required) | The type of extension |
fieldType | FieldExtensionType (required) | What field type is your extension targeting |
features | [FieldExtensionFeature] (required) | List of features implemented by the extension (at least one) |
fieldConfig | ConfigFields | Optional definition of field configuration settings. Supports the following field types: string, number, and boolean |
Supported FieldExtensionType enumeration values:
| Type | value type |
|---|---|
STRING | string |
INT | number (without decimals) |
FLOAT | number |
BOOLEAN | boolean |
JSON | any valid JSON value |
DATE | string in format 'yyyy-MM-dd' |
DATETIME | string in ISO 8601 format |
LOCATION | object { "latitude": number; "longitude": number; } |
COLOR | object { "rgba": { "r": number; "g": number; "b": number; "a": number; } } |
Soon to be supported FieldExtensionType values:
RICHTEXT, UNION, RELATION, ASSET
FieldRenderer: The extension replaces a form field.ListRenderer: By enabling this feature, you indicate
that the extension can handle array values as well, and that Hygraph should call
it directly instead of the default list renderer on multiple value inputs.TableRenderer: The extension should also be used to display values in the content table.