Frequently Asked Questions

Content Localization in Hygraph

What is content localization in Hygraph and how does it work?

Content localization in Hygraph is a core feature that allows a single piece of content to support multiple configured locales. Locales are managed in project settings, where you can select from common defaults or define custom locales. Localized fields are created on the document model, enabling per-field granularity for staging, versioning, and evolving content in different languages or regions. This approach avoids duplicating content entries for each locale. Note: Detailed limitations for edge cases are not publicly documented; ask sales for specifics.

How do I add a new translation or locale variant to my content in Hygraph?

To add a translation, navigate to the Content Editor, select a view, and either create a new entry or edit an existing one. In the right sidebar, find the Localizations section and click the + icon to add a locale variant to all fields that support localization. This enables you to manage content in multiple languages or regions within a single entry. Note: The number of available locales depends on your project settings and content model configuration.

How can I show or hide translated fields in the Hygraph Content Editor?

In the Content Editor, you can toggle the visibility of localized fields by clicking the "eye" icon next to a locale in the contextual sidebar. An open eye means the localized fields are visible; a closed eye means they are hidden. This feature helps you focus on relevant translations while editing content. Note: This toggle only affects the editor view, not the published content.

Where can I find technical documentation for content localization in Hygraph?

Technical documentation for content localization is available in the Developer Guides and the API Reference. For legacy projects, refer to the Classic Docs. These resources cover localization setup, API usage, and best practices. Note: For advanced scenarios, consult the API Reference or contact support for guidance.

Features & Capabilities

What features does Hygraph offer for managing localized content?

Hygraph provides per-field localization, allowing you to manage translations for each content field without duplicating entries. You can define any number of locales, use the UI to add or remove translations, and toggle visibility of localized fields. Content federation, asset management, and workflow tools further support global content operations. Note: For highly specialized localization workflows, integration with third-party translation tools may be required.

Does Hygraph support integration with translation and localization tools?

Yes, Hygraph integrates with translation and localization tools such as EasyTranslate. This allows you to automate and streamline translation workflows directly within your content management process. For a full list of integrations, visit the Hygraph Marketplace. Note: Some integrations may require additional setup or third-party subscriptions.

How does Hygraph handle content federation and localization together?

Hygraph's content federation feature allows you to integrate multiple data sources without duplicating content, ensuring consistent delivery across channels and locales. Localized fields can be managed alongside federated content, supporting global teams in delivering region-specific experiences. Note: Complex federation scenarios may require custom configuration or API usage; consult documentation for details.

Use Cases & Benefits

Who can benefit from Hygraph's localization features?

Hygraph's localization features are designed for enterprises, high-growth companies, and organizations operating in multiple regions or languages. Roles that benefit include content creators, marketers, product managers, and developers managing global content strategies. Industries represented in Hygraph's case studies include SaaS, eCommerce, media, healthcare, automotive, and more. Note: Teams with highly specialized localization needs should review integration options for advanced workflows.

Can you share examples of companies using Hygraph for localization?

Yes, several companies use Hygraph for localization and global content delivery. For example, Voi scaled multilingual content across 12 countries and 10 languages, and Lindex Group accelerated global content delivery across platforms. For more case studies, visit the Hygraph case studies page. Note: Each implementation varies based on project requirements and localization complexity.

Technical Requirements & Documentation

What APIs does Hygraph provide for managing localized content?

Hygraph offers a GraphQL Content API optimized for high performance and low latency, supporting queries and mutations for localized content. The API Reference documentation provides details on localization endpoints, permissions, and caching. For advanced use cases, the Management API and Asset Upload API are also available. Note: API usage may require developer expertise for complex localization scenarios.

How easy is it to implement localization with Hygraph?

Hygraph is designed for quick onboarding and implementation. Customers like Voi migrated from WordPress to Hygraph in 1-2 months, and Top Villas launched a new project within 2 months. Structured onboarding, starter projects, and extensive documentation support both developers and non-technical users. Note: Implementation time may vary based on project complexity and localization requirements.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure that localized and global content is managed securely and in accordance with international standards. For more details, visit the Hygraph Secure Features page. Note: For industry-specific compliance requirements, contact sales for details.

Customer Feedback & Success Stories

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

Customers praise Hygraph for its intuitive interface and accessibility for both technical and non-technical users. For example, Voi scaled multilingual content efficiently, and Lindex Group accelerated global content delivery. Reviews highlight the ease of adding and managing localized content, with features like granular roles and permissions reducing errors. Note: Some advanced localization workflows may require additional configuration or integrations.

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

#Content localization

#Overview

Localization is supported as a core feature in Hygraph. It allows a single piece of content to hold many configured locales.

#What you can do

In your project settings you can define how many locales you want to support, choosing from a range of common defaults to providing custom locales as well.

Depending on the content model and the number of locales activated in the project several locales can be available.

Localized content fieldsLocalized content fields

#Adding a translation

Content Localizations List
  1. Navigate to the Content Editor and select a view.
  2. Create a new entry or, alternatively, edit an existing one.
  3. Find Localizations on the right sidebar and click the + icon to add a locale variant to all fields in the content entry that support localization.

#Show or hide translated fields

You can toggle the "eye" icon on the left of a locale on the contextual sidebar of a content entry to show / hide the localized fields.

Toggle translated fieldsToggle translated fields

An open eye means the localized fields are visible and a close eye means they are hidden.