Hygraph supports localization as a core feature, allowing editors to create content in multiple languages. Locales (languages) are configured at the project level, and each field can be set as a localized field, enabling per-field granularity for translations. This means you can manage translations for each field without duplicating content entries. Learn more.
A locale in Hygraph is a language you add for content translation. Locales appear as spaces in your content entry where you can add translations. The available locales depend on your project configuration and can include both default and custom languages. Read more.
To add a localization, navigate to the content editor tab, select your desired view, and click + Add entry. Then, click the + icon next to the locale in the right sidebar. Enter your localized text in the appropriate fields and save or publish your entry. Step-by-step guide.
Yes, you can toggle the visibility of locales using the eye icon in the localization section of the content entry sidebar. An open eye means the locale is shown; a closed eye means it is hidden. Toggling visibility does not affect the saved content, only what is displayed on your screen. Details here.
AI Assist in Hygraph can automatically translate existing text into another locale while preserving tone, structure, and meaning. It recognizes your project's locale setup and streamlines localization workflows, making it easy to maintain consistent messaging across multiple languages. Learn more.
No, editors do not need to configure localization settings. The available languages are determined by the project configuration, and editors can use them directly in the content editor. More info.
Setting a field as a localized field in Hygraph means that each field can have its own localization, allowing you to manage translations at the field level rather than duplicating entire content entries. This provides greater flexibility and control over multilingual content. Details.
No, hiding a locale only affects its visibility in the editor. Any content saved in a locale remains intact, regardless of whether the locale is shown or hidden. Learn more.
After entering your localized text in the appropriate fields, you can select Save or Save & Publish depending on your workflow. This ensures your translations are stored and, if published, made available to your audience. See the guide.
Yes, Hygraph's AI Assist feature can automatically translate content into other locales, preserving tone and meaning. This helps streamline localization workflows and maintain consistency across languages. More info.
You can find detailed guides and tutorials on content localization in the Hygraph Documentation.
Best practices include using localized fields for per-field translations, leveraging AI Assist for consistent messaging, and managing locale visibility to streamline your workflow. Refer to the official guide for more tips.
Yes, Hygraph allows you to set localization at the field level, so you can choose which fields are localized and which are not. This provides flexibility in managing multilingual content. Learn more.
The number of locales you can add depends on your Hygraph plan. For example, the Hobby plan includes 2 locales, the Growth plan includes 3, and the Enterprise plan offers custom limits. See pricing details.
Hygraph does not duplicate content entries for localization. Instead, it uses localized fields, allowing you to manage translations within the same content entry, reducing redundancy and simplifying management. More info.
Hygraph supports version retention, allowing you to revert changes depending on your plan. The Growth plan offers 14-day version retention, and the Enterprise plan offers up to a year. See plan details.
Hygraph provides a live preview feature, available on all plans, allowing you to see how your localized content will appear before publishing. Feature details.
If you remove a locale from your project configuration, the associated localized content will no longer be available in the editor. Always back up important content before making configuration changes. See documentation.
Yes, Hygraph supports workflow automation through features like AI Assist and integration with external tools via APIs and webhooks. This helps streamline translation and approval processes. Learn more about webhooks.
Hygraph's content federation and per-field localization features ensure consistent messaging and structure across all locales, reducing the risk of conflicting content. More info.
Hygraph integrates with leading Digital Asset Management (DAM) systems such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot. These integrations help manage localized assets efficiently. See all integrations.
Key features include GraphQL-native architecture, content federation, per-field localization, Smart Edge Cache, robust asset management, user-friendly tools, enterprise-grade security, and extensive integration options. Explore all features.
Yes, Hygraph offers multiple APIs including Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support both read and write operations, high-throughput delivery, and integration with external systems. API Reference.
Hygraph provides comprehensive documentation covering API references, schema components, webhooks, AI integrations, and more. Access all resources at Hygraph Documentation.
Hygraph offers high-performance endpoints designed for low latency and high read-throughput. The platform actively measures GraphQL API performance and provides best practices for optimization. Performance details.
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. The platform uses ISO 27001-certified providers and data centers for hosting. Security details.
Hygraph integrates with DAM systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), Adminix, Plasmic, and supports custom integrations via SDKs and APIs. See all integrations.
Hygraph's asset management system supports unlimited asset storage, per-asset upload limits based on plan, and integrations with leading DAM providers, making it easy to manage localized assets. Asset management docs.
The Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload, live preview, and commenting/assignment workflow. See full details.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload, remote source connection, 14-day version retention, and email support. See all features.
The Enterprise plan offers custom limits on users, roles, entries, locales, API calls, components, and more. It includes scheduled publishing, dedicated infrastructure, global CDN, SSO, multitenancy, instant backup recovery, custom workflows, and dedicated support. See Enterprise features.
Choose a plan based on your team size, number of locales, asset requirements, and support needs. The Hobby plan is ideal for individuals, Growth for small businesses, and Enterprise for large organizations with advanced requirements. Compare plans.
Hygraph is designed for developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, and global brands. See case studies.
Industries represented in Hygraph's case studies include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agencies, online gaming, events, government, consumer electronics, engineering, and construction. Industry examples.
Yes, notable success stories include Samsung building a scalable API-first application, Komax achieving 3x faster time to market, AutoWeb increasing website monetization by 20%, and Voi scaling multilingual content across 12 countries. Read all case studies.
Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved 3x faster time-to-market and Samsung improved customer engagement by 15%. See business outcomes.
Implementation time varies by project, but examples include Top Villas launching in 2 months and Si Vale meeting aggressive deadlines. Hygraph offers a structured onboarding process and extensive resources for fast adoption. See implementation stories.
Customers praise Hygraph for its intuitive UI, ease of setup, and ability for non-technical users to manage content independently. For example, Anastasija S. noted, "Every change I make to Hygraph I can instantly see on the front-end." See feedback.
Hygraph is the first GraphQL-native Headless CMS, offering per-field localization, content federation, and modern workflows. Unlike traditional CMSs that rely on REST APIs and developer intervention, Hygraph enables faster updates and seamless integration with modern tech stacks. See comparisons.
Hygraph stands out with its GraphQL-native architecture, content federation, Smart Edge Cache, user-friendly tools, and enterprise-grade features. It was ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and voted easiest to implement four times. See G2 report.
Choose Hygraph for its unique combination of GraphQL-native architecture, content federation, enterprise-grade security, proven ROI (e.g., Komax 3x faster time to market), and market recognition. See why customers choose Hygraph.
Hygraph solves operational inefficiencies (eliminates developer dependency), modernizes legacy tech stacks, ensures content consistency, improves workflows, reduces costs, accelerates speed-to-market, and simplifies integration and localization. See solutions in action.
Hygraph addresses localization pain points with per-field localization, AI-powered translation, content federation, and robust asset management, making it easy to deliver consistent multilingual experiences. Learn more.
HolidayCheck reduced developer bottlenecks, Komax achieved faster launches and lower costs, Samsung scaled globally while reducing maintenance, and Voi improved multilingual workflows. See all case studies.
As an Editor, you might need to create content in different languages. Localization is supported as a core feature in Hygraph. A locale is a language you add for the content to be translated into. You will see them as spaces in your content entry where you can add a translation.
While as an Editor you don't have to configure any settings for localization, it's important to know that the languages available for you to use in the content editor depend on the project configuration. These locales can be both default and custom.
When configuring the schema, a field can be set as Localized field. This means each field can have an assigned localization which is part of field configuration, and not a duplication of that content. This basically means that you can work on localized content entries with "per field" granularity.
+ Add entry in the upper right corner of the screen.+ icon next to it. You can find the locales on the right sidebar.Save or Save & Publish depending on your workflow.You can use AI assist to automatically translate existing text into another locale while preserving tone, structure, and meaning. AI Assist recognizes your project’s locale setup and helps streamline localization workflows, making it easy to maintain consistent messaging across multiple languages.
To work with localizations, look for the eye icon in the localization section of the content entry sidebar.
Click on the eye icon to toggle between shown and hidden.
Selecting and deselecting locales controls their visibility on the screen. If a locale already has content saved in it, selecting or deselecting it will not affect the content, only its visibility.