Frequently Asked Questions

UI Extensions: Field and Sidebar Extensions

What are UI extensions in Hygraph and how do they work?

UI extensions in Hygraph allow you to customize the content editor by adding custom fields (field extensions) or sidebar widgets (sidebar extensions). Field extensions are added to content models like default fields and require a display name and API ID. Sidebar extensions are added via the Schema editor and can be reordered or previewed in the content editor. Note: UI extensions are only available in Hygraph Classic and may not be supported in all future versions. Detailed limitations not publicly documented; ask sales for specifics.

How do I add a field UI extension to a content model in Hygraph?

To add a field UI extension, open the schema editor, select your content model, and pick your custom field from the list. The field will be grouped according to the fieldType specified in its declaration. You must provide a display name and API ID, and you can configure validation options as with default fields. Note: This process applies to Hygraph Classic. Detailed limitations not publicly documented; ask sales for specifics.

How do I add and customize sidebar extensions in Hygraph?

To add a sidebar extension, go to the Schema editor, select your model, and click the Sidebar tab. Under Sidebar Widgets, choose the widget you want to add and click Create. You can reorder widgets by dragging the handle. To preview, go to content editing, select your model, and add or edit an item. Note: Sidebar extensions are available in Hygraph Classic. Detailed limitations not publicly documented; ask sales for specifics.

Where can I find quickstart guides for building field and sidebar extensions?

Quickstart guides for building field extensions and sidebar extensions are available in the Hygraph Classic documentation: Field Extension Quickstart and Sidebar Extension Quickstart. Note: These guides are specific to Hygraph Classic. Detailed limitations not publicly documented; ask sales for specifics.

Features & Capabilities

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management (DAM) systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting and deployment platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and more. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional configuration or may not be available in all Hygraph versions. Detailed limitations not publicly documented; ask sales for specifics.

What APIs does Hygraph provide?

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. For details, see the API Reference documentation. Note: API availability and features may differ between Hygraph Classic and the current platform. Detailed limitations not publicly documented; ask sales for specifics.

What technical documentation is available for Hygraph users?

Hygraph provides extensive technical documentation, including API references, schema guides, integration instructions, and AI feature documentation. Key resources include the API Reference, Components Documentation, References Documentation, and Getting Started guides. Note: Documentation is version-specific; check if you are using Hygraph Classic or the current platform. Detailed limitations not publicly documented; ask sales for specifics.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international security and privacy standards. Note: Certification scope may differ between Hygraph Classic and the current platform. Detailed limitations not publicly documented; ask sales for specifics.

What security features does Hygraph offer?

Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups, secure APIs with custom origin policies and IP firewalls, and automatic backup and recovery. For more, see the Secure Features page. Note: Feature availability may differ between Hygraph Classic and the current platform. Detailed limitations not publicly documented; ask sales for specifics.

Implementation & Onboarding

How long does it take to implement Hygraph and how easy is it to start?

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. Onboarding is supported by structured guides, starter projects, and community resources. Sign up at app.hygraph.com/signup and explore Getting Started guides. Note: Migration complexity and onboarding experience may differ for Hygraph Classic. Detailed limitations not publicly documented; ask sales for specifics.

Use Cases & Customer Success

Who uses Hygraph and what industries are represented in your case studies?

Hygraph is used by companies such as Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. Industries include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. For details, see Hygraph's case studies. Note: Some case studies may reference Hygraph Classic; feature parity may differ. Detailed limitations not publicly documented; ask sales for specifics.

What business impact have customers seen with Hygraph?

Customers have reported faster time-to-market (Komax: 3x faster), improved customer engagement (Samsung: 15% increase), and increased website monetization (AutoWeb: 20% increase). Voi scaled multilingual content across 12 countries and 10 languages. For more, see Hygraph's case studies. Note: Results may vary by implementation and version. Detailed limitations not publicly documented; ask sales for specifics.

Product Performance & Limitations

How does Hygraph perform in terms of content delivery and API speed?

Hygraph has optimized its high-performance endpoints for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement. API performance is actively measured, with practical optimization advice available in the GraphQL Report 2024. Note: Performance may vary based on project configuration and version. Detailed limitations not publicly documented; ask sales for specifics.

Customer Experience & Feedback

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph for its intuitive interface, quick adaptability, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, and Anastasija S. (Product Content Coordinator) highlighted instant front-end updates. Charissa K. (Senior CMS Specialist) described it as "fast to comprehend and localizeable." Note: Feedback may reference Hygraph Classic; user experience may differ in newer versions. Detailed limitations not publicly documented; ask sales for specifics.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Hygraph
Classic Docs

#Using UI extensions

#Field extensions

To use a field UI extension in the content editor, add it to a content model like you would with default Hygraph fields. In schema editor, pick your custom field from the list. It will be grouped with other fields according to the fieldType value specified in the declaration.

Available Fields with UI extensionAvailable Fields with UI extension

Just like any other field, it will need a display name and an API ID. Default validation and configuration options are available to custom fields as well.

Add UI ExtensionAdd UI Extension

Once your custom field is ready, go to content editing and add a new entry. You should now see your custom UI extension rendered:

UI Extension Field RendererUI Extension Field Renderer

To use a Sidebar Extension in the content editor sidebar, do the following steps:

#Customizing sidebar widgets

  1. Go to Schema editor
  2. Click on the model you would like to edit
  3. Below model's name, click on Sidebar tab
  4. Under Sidebar Widgets, click on the widget you would like to add
  5. Click on Create to finish

#Previewing your customized sidebar

  1. Go to Content or click on Go to content editing link at the top right corner
  2. Click on the model you've edited in the previous step
  3. Click on Add New Item or edit an existing one

Now, you should see your customized sidebar and can use your sidebar extensions.

#Next steps