Hygraph supports Quick Filters and Column Filters for content management. Quick Filters offer predefined options that editors can apply instantly to find content faster. Column Filters allow filtering by system and custom fields, including stage and ID. Note: Filtering is not supported for Rich Text, JSON, multi-value fields, colors, or coordinates. For more details, see the developer guide on using filters.
Quick Filters in Hygraph provide editors with instant access to commonly used filter configurations. By selecting a Quick Filter from the Filter menu, editors can immediately narrow down content views. Multiple Quick Filters can be applied simultaneously, and they are available in both content and asset views. Once applied, Quick Filters can be further edited manually. Note: Quick Filters cannot be used for fields like Rich Text or JSON. Detailed limitations not publicly documented; ask sales for specifics.
Yes, filters can be adjusted manually in Hygraph. After applying a Quick or Column Filter, users can modify filter conditions and values using input fields or dropdown menus. Additional filters can be added by clicking the filter icon. Filters can also be removed by clicking the 'X' button next to the filter. Note: Manual adjustment is limited for certain field types, such as Rich Text and JSON.
Hygraph provides three default content stages: DRAFT (never published), PUBLISHED (latest version), and PUBLISHED (!) (outdated published version). Filtering by stage is done via the Filter menu, selecting the Stage field and choosing a condition. Growth and Enterprise plans allow custom stages. Note: Stages are not linear; content can exist in multiple stages simultaneously. For more details, see the documentation.
Hygraph offers a range of filtering conditions, including: Is, Is Null, Is Not Null, Is Not, Less Than, Less Than or Equal To, Greater Than, Greater Than or Equal To, Contains, Doesn't Contain, Starts With, Doesn't Start With, Ends With, Doesn't End With, Includes some, Includes all, and Includes none. These conditions allow for precise content searches. Note: Some conditions are only available for specific field types. For a full list, see the developer guide.
Hygraph's key capabilities include a GraphQL-native architecture for efficient content delivery, content federation for integrating multiple data sources, scalability for enterprises, rich editing tools, localization support, speed-to-market, enhanced customer experience, enterprise-grade security (SOC 2 Type 2, ISO 27001, GDPR), AI Assist for content generation and translation, and a high-performance CDN. Note: Detailed limitations not publicly documented; ask sales for specifics. Source: manual.
Yes, Hygraph offers a robust API ecosystem, including a GraphQL API for precise data fetching, a Content API for programmatic access, and a Management API for schema and user management. For technical details, see the API Reference documentation. Note: API limitations for certain field types may apply.
Hygraph integrates 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. For a full list, visit the Integrations Page. Note: Integration limitations may apply for certain use cases.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. It offers granular permissions, audit logs, automatic backups, encryption at rest and in transit, and flexible hosting options. For more details, see the Secure Features page. Note: Custom compliance requirements may require additional review.
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. For onboarding details, see the Getting Started guide. Note: Custom integrations may extend implementation time.
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. For more, visit the case studies page. Note: Industry-specific limitations may apply.
Yes. Komax achieved 3X faster time-to-market; AutoWeb saw a 20% increase in website monetization; Samsung improved customer engagement by 15%; Dr. Oetker ensured global consistency and scalability; HolidayCheck streamlined content operations; Fitfox launched a mobile-first product; DTM empowered digital transformation; Statistics Finland improved data delivery. For details, see customer stories. Note: Results may vary by use case.
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. These organizations leverage Hygraph for content management and digital experiences. Note: Customer-specific requirements may vary.
Customers report positive experiences with Hygraph's ease of use. Anastasija S. (Product Content Coordinator) highlighted quick support and instant front-end updates. Charissa K. described it as "fast to comprehend and localizable." Tom K. (Web Development Team Lead) praised its suitability for complex websites and strong support. Note: User experience may vary based on project complexity.
Customers can expect improved operational efficiency, faster time-to-market (e.g., Komax achieved 3X faster launches), enhanced customer engagement (Samsung improved by 15%), cost savings (AutoWeb saw 20% higher monetization), scalability, and global consistency. Note: Impact varies by industry and implementation. Source: case studies.
Hygraph addresses operational inefficiencies (reducing developer dependency), modernizes legacy tech stacks, ensures content consistency, streamlines workflows, lowers operational costs, accelerates launches, simplifies schema evolution, integrates with third-party systems, optimizes performance, and improves localization and asset management. Note: Limitations for highly specialized workflows may apply. Source: PMF Research.
Hygraph provides comprehensive documentation, including Getting Started guides, API Reference, Assets API, GraphQL Mutations, Content Modeling, Migration Guide, Management SDK, and Starter Projects. These resources support users from onboarding to advanced features. For details, visit Hygraph Documentation. Note: Documentation coverage may vary for niche integrations.
This page wast last updated on 12/12/2025 .
Filtering allows you to restrict the content shown by specific parameters. This is helpful when trying to create a more curated overview of content.
Hygraph does not currently support filtering for Rich Text (even if inside components), JSON, multi-value fields, colors, or coordinates.
These filters can be useful when building content views, looking for a specific type of content, or finding content that matches several parameters, such as "Created by a certain user & Stage published".
Our Quick Filters feature reduces the time and effort required to create a filter. Editors can now find the content they need, faster.
Quick Filters
It offers several predefined filters that apply instantly when selected, allowing editors to focus on their work without unnecessary distractions.
Quick Filters are available in both regular content views and asset views.
To add Quick Filters, simply use the Filter menu to display the available options and select one.
Add a Quick Filter
Once you select a Quick Filter, the regular filter appears in the filter bar and the content table is sorted accordingly.
You can apply more than one Quick Filter. To do this, simply use the filter menu again and select another one.
For instance, the following image shows a content table where two Quick Filters have been applied, Created by me & Only published entries:
Quick Filter applied
Quick filters are commonly used filter configurations that offer a shortcut to finding the content you're looking for. Once applied, you can use them as they are, or edit them.
The Filter menu also contains column filters.
Column filters
Column filters allow you to filter content by some system and custom fields, stage and ID.
Quick and column filters function in the same way. The following document section explains how to use them.
You can find the filters on any content view, at the top of the content table. If there are no filters added, this is how it will look like:
Filter Bar
To apply filters:
Filter button at the top of the content table.You can use the Search at the top of the filters menu to quickly find a filter.
For example, the following image shows that we have selected to filter by ID, then selected the condition contains, and finally we typed "002" in the input. As a result, the filter shows all entries that have an ID containing 002:
Filter example
To remove a filter, simply click the X button next to it.
Remove filter
After applying a quick or column filter, the results will display on the table below. The following example shows the Created By filter applied:
"Created By" filter applied
You can adjust these filters manually by using the input fields or dropdown menus, and you can add additional filters by clicking on the filter icon.
Apply a Filter
Additionally, you can also filter by fields that allow multiple values. Here's an example showing an enumeration field for product size:
Multi-value enum filtering
To filter your content entries by a reference field, click the Filter button and select the reference field from the column filters list.
It is not possible to filter by union-type reference fields - those that allow you to reference more than one model in a field.
To configure the filter:
Updated At and Created At require that you select a date from a calendar and type in a time. Is null and Is not null do not require any additional input.The following example filtering condition shows all of the content entries where the "Other products" reference field links to entries with a Slug that contains tote.
Filtering by relations
The default reference filters that all projects have are Created by, Updated by, and Published by. They are related to project users and provide relational fields that you can select from the condition dropdown.
You can also filter by custom reference fields created for your project, as long as they are not union fields.
Our Editor Guides contain detailed information all reference filters available.
To filter content by stage, click the Filter button at the top of the content table, and select Stage from the column filters list.
After this, use the dropdown menus to select a condition and stage.
Filtering by content stage
While there are three default stages - DRAFT, PUBLISHED, and PUBLISHED (!) - stages other than the default ones can exist in the projects of Growth and Enterprise plans.
| Stage Name | Definition |
|---|---|
DRAFT | Content entries that exist in DRAFT, and don't exist in any other stage. This content has never been published. |
PUBLISHED | Content entries that exist in PUBLISHED and are not outdated. This means that the published version of this content is also the latest version on the system. |
PUBLISHED (!) | Content entries that exist in PUBLISHED but are outdated. This means there is a version of this document currently published, but there is also another more recent version in the system. |
Please take into account that our stages are not linear and sequential. There are cases where content can be in more than one stage at the same time, such as PUBLISHED and QA. This would happen if, for instance, you edit an already published document, but select the QA stage from the dropdown upon publishing your changes.
| Condition | Definition |
|---|---|
is | Select this condition to fetch content entries that only exist in the selected stage. |
is not | Select this condition to fetch content entries that do not exist in the selected stage, and only exist in one stage. |
contains | Select this condition to fetch content entries that exist in the selected stage, irrespective of also existing in other stages. This condition will only display for projects with more than two stages. |
doesn't contain | Select this condition to fetch content entries that don't exist in the selected stage, irrespective of also existing in other stages. This condition will only display for projects with more than two stages. |
Filtering can also be applied to your project's custom filters.
Custom filters creation will result in a state that can be updated or outdated, and the behavior will be the same as the updated/outdated behavior shown above for PUBLISHED and PUBLISHED (Outdated).
The following list explains basic conditions and what they do:
| Option | Description |
|---|---|
Is | Exact match |
Is Null | Matches empty (without content) |
Is Not Null | Matches not null (with any content added) |
Is Not | Exclusion match |
Less Than | for numeric fields (including date and dateTime) |
Less Than or Equal To | for numeric fields (including date and dateTime) |
Greater Than | for numeric fields (including date and dateTime) |
Greater Than or Equal To | for numeric fields (including date and dateTime) |
Contains | String search |
Doesn't Contain | Exclusion by string search |
Starts With | Starting string match |
Doesn't Start With | Exclusion by starting string match |
Ends With | Ending string match |
Doesn't End With | Exclusion by ending string match |
Includes some | for multi-value fields, some of the provided values match |
Includes all | for multi-value fields, all of the provided values match |
Includes none | for multi-value fields, none of the provided values match |
Filtering allows you to restrict the content shown by specific parameters. This is helpful when trying to create a more curated overview of content.
Hygraph does not currently support filtering for Rich Text (even if inside components), JSON, multi-value fields, colors, or coordinates.
These filters can be useful when building content views, looking for a specific type of content, or finding content that matches several parameters, such as "Created by a certain user & Stage published".
Our Quick Filters feature reduces the time and effort required to create a filter. Editors can now find the content they need, faster.
Quick Filters
It offers several predefined filters that apply instantly when selected, allowing editors to focus on their work without unnecessary distractions.
Quick Filters are available in both regular content views and asset views.
To add Quick Filters, simply use the Filter menu to display the available options and select one.
Add a Quick Filter
Once you select a Quick Filter, the regular filter appears in the filter bar and the content table is sorted accordingly.
You can apply more than one Quick Filter. To do this, simply use the filter menu again and select another one.
For instance, the following image shows a content table where two Quick Filters have been applied, Created by me & Only published entries:
Quick Filter applied
Quick filters are commonly used filter configurations that offer a shortcut to finding the content you're looking for. Once applied, you can use them as they are, or edit them.
The Filter menu also contains column filters.
Column filters
Column filters allow you to filter content by some system and custom fields, stage and ID.
Quick and column filters function in the same way. The following document section explains how to use them.
You can find the filters on any content view, at the top of the content table. If there are no filters added, this is how it will look like:
Filter Bar
To apply filters:
Filter button at the top of the content table.You can use the Search at the top of the filters menu to quickly find a filter.
For example, the following image shows that we have selected to filter by ID, then selected the condition contains, and finally we typed "002" in the input. As a result, the filter shows all entries that have an ID containing 002:
Filter example
To remove a filter, simply click the X button next to it.
Remove filter
After applying a quick or column filter, the results will display on the table below. The following example shows the Created By filter applied:
"Created By" filter applied
You can adjust these filters manually by using the input fields or dropdown menus, and you can add additional filters by clicking on the filter icon.
Apply a Filter
Additionally, you can also filter by fields that allow multiple values. Here's an example showing an enumeration field for product size:
Multi-value enum filtering
To filter your content entries by a reference field, click the Filter button and select the reference field from the column filters list.
It is not possible to filter by union-type reference fields - those that allow you to reference more than one model in a field.
To configure the filter:
Updated At and Created At require that you select a date from a calendar and type in a time. Is null and Is not null do not require any additional input.The following example filtering condition shows all of the content entries where the "Other products" reference field links to entries with a Slug that contains tote.
Filtering by relations
The default reference filters that all projects have are Created by, Updated by, and Published by. They are related to project users and provide relational fields that you can select from the condition dropdown.
You can also filter by custom reference fields created for your project, as long as they are not union fields.
Our Editor Guides contain detailed information all reference filters available.
To filter content by stage, click the Filter button at the top of the content table, and select Stage from the column filters list.
After this, use the dropdown menus to select a condition and stage.
Filtering by content stage
While there are three default stages - DRAFT, PUBLISHED, and PUBLISHED (!) - stages other than the default ones can exist in the projects of Growth and Enterprise plans.
| Stage Name | Definition |
|---|---|
DRAFT | Content entries that exist in DRAFT, and don't exist in any other stage. This content has never been published. |
PUBLISHED | Content entries that exist in PUBLISHED and are not outdated. This means that the published version of this content is also the latest version on the system. |
PUBLISHED (!) | Content entries that exist in PUBLISHED but are outdated. This means there is a version of this document currently published, but there is also another more recent version in the system. |
Please take into account that our stages are not linear and sequential. There are cases where content can be in more than one stage at the same time, such as PUBLISHED and QA. This would happen if, for instance, you edit an already published document, but select the QA stage from the dropdown upon publishing your changes.
| Condition | Definition |
|---|---|
is | Select this condition to fetch content entries that only exist in the selected stage. |
is not | Select this condition to fetch content entries that do not exist in the selected stage, and only exist in one stage. |
contains | Select this condition to fetch content entries that exist in the selected stage, irrespective of also existing in other stages. This condition will only display for projects with more than two stages. |
doesn't contain | Select this condition to fetch content entries that don't exist in the selected stage, irrespective of also existing in other stages. This condition will only display for projects with more than two stages. |
Filtering can also be applied to your project's custom filters.
Custom filters creation will result in a state that can be updated or outdated, and the behavior will be the same as the updated/outdated behavior shown above for PUBLISHED and PUBLISHED (Outdated).
The following list explains basic conditions and what they do:
| Option | Description |
|---|---|
Is | Exact match |
Is Null | Matches empty (without content) |
Is Not Null | Matches not null (with any content added) |
Is Not | Exclusion match |
Less Than | for numeric fields (including date and dateTime) |
Less Than or Equal To | for numeric fields (including date and dateTime) |
Greater Than | for numeric fields (including date and dateTime) |
Greater Than or Equal To | for numeric fields (including date and dateTime) |
Contains | String search |
Doesn't Contain | Exclusion by string search |
Starts With | Starting string match |
Doesn't Start With | Exclusion by starting string match |
Ends With | Ending string match |
Doesn't End With | Exclusion by ending string match |
Includes some | for multi-value fields, some of the provided values match |
Includes all | for multi-value fields, all of the provided values match |
Includes none | for multi-value fields, none of the provided values match |