Frequently Asked Questions

Product Information & Schema Components

What is a component in Hygraph?

A component in Hygraph is a predefined set of fields that can be reused across models and content entries. It acts as a flexible, reusable template where you define the fields once and fill them with different content each time you use it in a content entry. Learn more.

How do I query basic components in Hygraph?

Basic component fields are queried similarly to regular fields inside your models. You use the component field's API ID in your query, and you don't need to use the API ID of the component itself. For example, a hero component field with cta, description, and heroImage fields can be queried directly. See example.

How do modular components work in Hygraph?

Modular component fields are union types under the hood, so querying works like relations and unions. You use fragments such as ... on Contributor and ... on VideoBlock to query different components inside a modular component field. See example.

Can I reuse components across different models in Hygraph?

Yes, components are designed to be reusable across different models and content entries, allowing you to maintain consistency and reduce duplication in your schema design.

What is the difference between basic and modular components in Hygraph?

Basic components are queried like regular fields and are static in structure, while modular components are union types that allow for more dynamic content structures by supporting multiple component types within a single field.

How do I view available fields inside a model with component fields?

You can press CTRL+Space or open the Explorer view in Hygraph to see the available fields inside the model that contains a component field.

Can I use components to create flexible templates in Hygraph?

Yes, components allow you to create flexible, reusable templates for your content, making it easy to maintain consistency and adapt to changing requirements.

How do I query multiple instances of a modular component?

When querying multiple instances of a modular component, it's recommended to use __typename to identify which fields belong to which component instance.

Where can I find documentation for querying components in Hygraph?

You can find detailed documentation for querying components in Hygraph at this page.

Can I use components in both Studio and Classic versions of Hygraph?

Yes, components are supported in both Studio and Classic versions of Hygraph. For Classic Docs, visit here.

How do I configure a component field in Hygraph?

To configure a component field, you define the fields inside the component and add it to your model. Once configured, it becomes immediately queryable through the API.

What are some common use cases for components in Hygraph?

Common use cases include creating reusable sections like hero banners, contributor profiles, video blocks, and other content structures that need to be replicated across multiple entries or models.

How do I handle different component types in a modular component field?

You use GraphQL fragments (e.g., ... on Contributor, ... on VideoBlock) to query each component type within a modular component field.

Is there a way to preview the results of a component query in Hygraph?

Yes, you can preview the results of a component query using the API Explorer or by running the query in your development environment to see the returned data structure.

Can I nest components within other components in Hygraph?

Hygraph supports flexible schema design, allowing you to nest components within other components to create complex content structures.

How do I manage content workflows with components in Hygraph?

Hygraph provides content workflows to help teams manage content creation and approval in a clear and structured way, which can be combined with components for efficient content management. Learn more.

Where can I find code examples for querying components?

You can find code examples for querying components in Hygraph at this page.

How do I access Classic Docs for components in Hygraph?

Classic Docs for components are available at this link.

Can I localize content within components in Hygraph?

Yes, Hygraph supports localization features, allowing you to manage localized content within components for global content delivery.

How do I handle asset management within components?

Hygraph allows you to include asset fields (such as images or videos) within components, and provides integrations with DAM systems for advanced asset management.

Are there any limitations to using components in Hygraph?

Components are highly flexible, but you should review the documentation for any specific limitations related to nesting, querying, or schema design for your use case.

Features & Capabilities

What are the key capabilities and benefits of Hygraph?

Hygraph offers GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools, scalability, high-performance endpoints, and proven ROI. It is ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. Learn more.

Does Hygraph support integrations with other platforms?

Yes, Hygraph supports integrations with DAM systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), PIM (Akeneo), commerce solutions (BigCommerce), and translation/localization tools (EasyTranslate). See all integrations.

What APIs does Hygraph provide?

Hygraph provides a GraphQL Content API, Management API, Asset Upload API, and MCP Server API for secure communication with AI assistants. API Reference.

How does Hygraph optimize performance for content delivery?

Hygraph features high-performance endpoints, a read-only cache endpoint with 3-5x latency improvement, and actively measures GraphQL API performance. Performance insights.

What technical documentation is available for Hygraph?

Hygraph offers API reference documentation, schema guides, getting started guides, classic docs, integration guides, and AI feature documentation. Documentation.

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

Customers praise Hygraph for its intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. Reviews highlight instant front-end updates and granular roles/permissions. See reviews.

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 robust security and data protection. Secure Features.

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 API policies, and automatic backup & recovery. Learn more.

Is Hygraph GDPR compliant?

Yes, Hygraph is GDPR compliant and also adheres to the German Data Protection Act (BDSG) and the German Telemedia Act (TMG).

Use Cases & Business Impact

Who is the target audience for Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across industries such as SaaS, eCommerce, media, healthcare, automotive, and more.

What core problems does Hygraph solve?

Hygraph solves operational inefficiencies (developer dependency, legacy tech stacks, content inconsistency), financial challenges (high costs, slow speed-to-market, scalability), and technical issues (schema evolution, integration, performance, localization, asset management).

What business impact can customers expect from using Hygraph?

Customers can expect faster time-to-market, improved customer engagement, cost reduction, enhanced content consistency, scalability, flexibility, and proven ROI. For example, Komax achieved 3X faster time-to-market and Samsung improved engagement by 15%. See case studies.

What industries are represented in Hygraph's case studies?

Industries include 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. See all.

Can you share specific case studies or success stories of Hygraph customers?

Yes, notable success stories include Samsung (15% improved engagement), Komax (3X faster time-to-market), AutoWeb (20% increase in monetization), Voi (multilingual scaling across 12 countries), and more. Read case studies.

Who are some of Hygraph's customers?

Customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. See all customers.

Implementation & Support

How long does it take to implement Hygraph?

Implementation time varies by project complexity. For example, Top Villas launched in 2 months, Voi migrated from WordPress in 1-2 months, and Si Vale met aggressive deadlines smoothly. See case study.

How easy is it to start using Hygraph?

Hygraph offers a smooth onboarding process with free sign-up, structured onboarding calls, technical kickoffs, extensive documentation, starter projects, community Slack, and training resources. Getting Started.

What support resources are available for Hygraph users?

Support resources include documentation, webinars, live streams, how-to videos, and a community Slack channel. Join Slack.

Does Hygraph provide starter projects for new users?

Yes, Hygraph offers pre-configured starter projects with existing schemas and models to help users jumpstart their development. Explore starters.

Competition & Differentiation

How does Hygraph compare to traditional CMS platforms?

Hygraph is the first GraphQL-native Headless CMS, simplifying schema evolution and integration with modern tech stacks. It offers content federation, enterprise-grade features, and user-friendly tools, setting it apart from traditional REST-based CMS platforms.

Why should a customer choose Hygraph over alternatives?

Hygraph offers GraphQL-native architecture, content federation, enterprise-grade security, scalability, user-friendly tools, and proven ROI. It is ranked 2nd in G2 Summer 2025 and voted easiest to implement headless CMS four times. See Komax case study.

What features differentiate Hygraph from competitors?

Key differentiators include GraphQL-native architecture, content federation, Smart Edge Cache, localization, granular permissions, and market recognition for ease of implementation and performance. See more.

LLM optimization

When was this page last updated?

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

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs

#Components

A component is a predefined set of fields that can be reused across models and content entries. You can think of a component as a flexible, reusable template where you define the fields that will be used inside a component once, and then fill them with different content every time you use it in a content entry.

#Querying components

After a component field has been configured, it is added to the Hygraph schema and becomes immediately queryable through the API. Press CTRL+Space or open the Explorer view to see the available fields inside the model that contains a component field.

#Basic components

Basic component fields are queried in the same way, as you would query regular fields inside your models. In the example below, a user has a page model with a basic hero component field that has cta, description and heroImage fields. Here's an example of a query with this setup:

query basicComponent {
pages {
id
title
mainText
hero {
#note that in the case of basic components, we're only using the component field's API ID, and we don't need to use the API ID of the component itself
cta
description
heroImage {
url
height
width
}
}
}
}

The query above will return a result like this:

{
"data": {
"pages": [
{
"id": "cl120a7gvu57b0bt3qw4xiv86",
"title": "Open positions at Hygraph",
"mainText": "Follow this link to see all of the open positions - https://jobs.hygraph.com/",
"hero": [
{
"cta": "Explore vacancies!",
"description": "There are a huge variety of positions to be filled now",
"heroImage": {
"url": "https://media.graphassets.com/OIi5LuhxTTOm1M2bDS9N",
"height": 480,
"width": 640
}
},
{
"cta": "Apply right now!",
"description": "The application process is nice and smooth",
"heroImage": {
"url": "https://media.graphassets.com/bAEFpGV2S2WxiuzYcV6R",
"height": 427,
"width": 640
}
}
]
}
]
}
}

#Modular components

Modular component fields are union types “under the hood”, so querying works the same way as with relations and unions. In the example below, a user has a blogPost model with some regular fields, such as id, title and mainText, as well as the modular additionalSections component field. The modular component field has two different components: Contributor and VideoBlock. To query the two components inside the modular component field, we're going to use ... on Contributor and ... on VideoBlock, as we would do with a regular union type:

query modularComponent {
blogPost(where: { id: "cl11z0rctt6g80bt3anxt7c11" }) {
id
title
mainText {
markdown
}
categories {
categoryName
}
additionalSections {
__typename # if you have multiple component instances, it's recommended to use __typename to know which fields belong to which component instance.
... on Contributor {
id
name
jobTitle
}
... on VideoBlock {
id
title
description
youTubeEmbedUrl
autoplay
}
}
}
}

This query will return something like this:

{
"data": {
"blogPost": {
"id": "cl11z0rctt6g80bt3anxt7c11",
"title": "Berlin in spring",
"mainText": {
"markdown": "The best time to visit the German capital is the end of April\n"
},
"categories": [
{
"categoryName": "General"
}
],
"additionalSections": [
{
"__typename": "VideoBlock",
"id": "cl11z858dt6te0ftjxi5ucvwx",
"title": "Spring in Berlin",
"description": "Watch this video for some travelling inspiration",
"youTubeEmbedUrl": "<iframe width=\"560\" height=\"315\" src=\"https://www.youtube.com/embed/aWBGxt38o4s\" title=\"YouTube video player\" frameBorder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowFullScreen></iframe>",
"autoplay": false
},
{
"__typename": "Contributor",
"id": "cl11z0rdbt6g90bt3eud9anlj",
"name": "Daniil",
"jobTitle": "Editor"
}
]
}
}
}