Frequently Asked Questions

Integration Setup & Prerequisites

What is the Hygraph-Lokalise integration?

The Hygraph-Lokalise integration connects your Hygraph project with Lokalise, a localization management platform. This integration enables teams to manage workflows for multiple locales and translations, allowing for collaborative localization, high-quality translations, and the creation of new locales for digital products such as applications and websites. Learn more.

What are the prerequisites to use the Hygraph-Lokalise integration?

To use the Hygraph-Lokalise integration, you need:

For more details, see the official prerequisites.

How do I install the Lokalise app in Hygraph?

To install the Lokalise app in Hygraph:

  1. Go to the Hygraph Marketplace and select the project for installation.
  2. Enter your Lokalise API token and Project ID.
  3. Select at least one model to use Lokalise with (this can be edited later).
  4. Click Save to complete the installation.
Step-by-step instructions are available in the documentation.

What permissions or tokens are required for the integration?

You need a Lokalise API token to connect your Hygraph project to Lokalise. This token can be generated in your Lokalise account settings. Learn how to create a Lokalise API token.

Are apps in Hygraph environment-specific?

Yes, apps in Hygraph are environment-specific. Their configuration applies per environment, so if you use multiple environments in your project, you need to configure the app for each one separately.

Features & Capabilities

What can I do with the Hygraph-Lokalise integration?

The integration allows you to bulk import and export content between Hygraph and Lokalise, manage multiple locales, and streamline localization workflows directly within the Hygraph interface. You can export content for translation, import completed translations, and monitor translation statuses. More info.

Which field types are supported for export and import with Lokalise?

The following field types are supported for export and import: Single-line text, Multi-line text, Markdown, Richtext, and Slug. Basic and Modular Components are also supported, but only for these field types. Details here.

How do I export content from Hygraph to Lokalise?

To export content:

  1. Go to the Content editor in Hygraph.
  2. Select Lokalise under App views.
  3. Choose the content to export and click 'Submit to Translate'.
  4. Select the locales and click 'Export translation'.
The status will update to 'In progress' and the content will be available in Lokalise for translation. Step-by-step guide.

How do I import translations from Lokalise into Hygraph?

After translations are completed in Lokalise, go to the Lokalise section in the Hygraph Content editor, select the entries, and click 'Import Translation'. Choose the languages to import and confirm. The status will update to 'Imported'. Full instructions.

How can I view the translation status of my content?

The Lokalise app view in the Hygraph Content editor displays the localization status for each entry, including statuses like Missing, In progress, Done, Changed, and Imported. This helps you track which content has been sent, translated, or imported. See status definitions.

Can I edit which models use Lokalise after installation?

Yes, you can edit which models use Lokalise by navigating to Apps > Lokalise in your Hygraph project, clicking the pencil icon, and updating your selections.

Are only localizable fields supported for translation with Lokalise?

Yes, only fields set as localized in your model can be submitted to Lokalise for translation. You can set a field as localizable in the Schema editor by checking the 'Localized field' option.

What do the different translation statuses mean?

The statuses are:

See the documentation for more details.

How do I view and manage translations in Hygraph after importing?

Navigate to the content editor, select the relevant model, and edit the entry. The Localizations section in the right sidebar allows you to add, delete, or view translations for each locale.

What should I do if I see 'This model has no localized fields' in the Content Editor?

If you see this message, check your Project settings > Locales and ensure you have at least two languages configured. Free plans support a maximum of 2 locales.

Where can I find more resources about the Lokalise integration?

You can find more resources in the Lokalise documentation and the Hygraph-Lokalise integration guide.

Pricing & Plans

What does the Hygraph Hobby plan cost and what does it include?

The Hygraph Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload size, live preview, and commenting/assignment workflow. See full details.

What features are included in the Growth plan and what is the cost?

The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload size, remote source connection, 14-day version retention, and email support. More info.

What does the Enterprise plan offer?

The Enterprise plan offers custom pricing and includes custom limits on users, roles, entries, locales, API calls, components, and more. It provides advanced features like scheduled publishing, dedicated infrastructure, SSO, multitenancy, instant backup recovery, custom workflows, and dedicated support. See all features.

How many locales can I use with each Hygraph plan?

The Hobby plan supports up to 2 locales, the Growth plan supports 3 locales, and the Enterprise plan offers custom limits on locales. See plan comparison.

Use Cases & Benefits

Who can benefit from the Hygraph-Lokalise integration?

Teams managing multilingual content for digital products, such as developers, content managers, and localization specialists, benefit from this integration. It streamlines translation workflows and ensures high-quality, consistent content across locales.

What business impact can customers expect from using Hygraph?

Customers can expect improved operational efficiency, faster speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved a 3X faster time-to-market and Samsung improved customer engagement by 15% using Hygraph. See case studies.

What are some real-world examples of companies using Hygraph?

Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. These companies have used Hygraph to scale content, reduce bottlenecks, and improve workflows. Read their stories.

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 case studies.

How long does it take to implement Hygraph?

Implementation time varies by project. For example, Top Villas launched a new project in just 2 months, and Si Vale met aggressive deadlines with a smooth rollout. Hygraph offers a free API playground, structured onboarding, and extensive documentation to support fast adoption. See details.

Technical Requirements & Troubleshooting

What should I do if my content is not appearing in the Lokalise section?

Ensure that the content was created using a model selected during Lokalise installation and that the fields are set as localized. You can edit model selection in Apps > Lokalise and update field localization in the Schema editor.

What are common troubleshooting steps for the Hygraph-Lokalise integration?

If you encounter issues, check that your project has at least two locales configured, fields are set as localized, and the correct models are selected for Lokalise. For free plans, only 2 locales are supported. See troubleshooting guide.

Where can I find technical documentation for Hygraph integrations?

Comprehensive technical documentation is available at Hygraph Integrations Documentation and Hygraph Documentation.

Does Hygraph provide an API for integrations?

Yes, Hygraph provides multiple APIs, including Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. See API Reference.

What other integrations does Hygraph support?

Hygraph supports integrations with DAM systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), Adminix, Plasmic, and custom integrations via SDKs and APIs. See all integrations.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure high standards for security and data protection. See details.

What enterprise-grade security features does Hygraph offer?

Hygraph offers granular permissions, audit logs, SSO integrations, encryption at rest and in transit, regular backups, and dedicated hosting options in multiple regions. Learn more.

Performance & Customer Feedback

How does Hygraph perform in terms of API speed and reliability?

Hygraph provides high-performance endpoints designed for low latency and high read-throughput content delivery. Performance is actively measured and optimized, as detailed in the performance improvements blog and GraphQL Survey 2024.

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

Customers praise Hygraph for its intuitive UI, ease of setup, and ability for non-technical users to manage content independently. For example, Anastasija S., Product Content Coordinator, said, "Every change I make to Hygraph I can instantly see on the front-end." See more feedback.

How does Hygraph help solve common content management pain points?

Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, and integration difficulties. Its user-friendly tools, content federation, and robust APIs help resolve these issues. See case studies.

How does Hygraph differentiate itself from other CMS platforms?

Hygraph is the first GraphQL-native Headless CMS, offering content federation, user-friendly tools, enterprise-grade features, and proven ROI. It was ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and is recognized for ease of implementation. See comparisons.

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

#Connect your Hygraph project to Lokalise

Lokalise is a localization management platform where teams can easily build and manage workflows for multiple locales and translations of existing content. It enables teams to build collaborative workflows around localization, ensure high quality translations are pushed live, and create new locales for a wide range of digital products, from applications to websites.

#What you can do with the Hygraph-Lokalise integration

  • With the Hygraph-Lokalise integration, teams can simplify their workflows between Lokalise and Hygraph by creating bulk imports and exports of content and easily manage multiple locales for their digital products through a dedicated interface within Hygraph.

#Prerequisites to use this integration

  • You must have a Hygraph account. If you don't have one, you can create one here.
  • You must have a Hygraph project.
  • You must have a Lokalise account. If you don't have one, you can create one here.
  • You must have a Lokalise project. The project type must be Software localization, and you must select a base language for your project in your project settings.
  • You must create a Lokalise API Token.

#Install the Lokalise app

Click here to install the Lokalise App on Hygraph, then follow these steps:

Lokalise installationLokalise installation

  1. In the dropdown, select which project you want to install the app in, then click on the Add App button. You should be redirected to your Hygraph project dashboard.
  2. Fill in the API token and the Project ID. This information can be found in your Lokalise account. The Hygraph UI provides links that show you how to get the information you need next to each requested field.
  3. Select at least one model to use Lokalise in. This information can be edited later by going to the Apps section of your Hygraph project, then clicking on the pencil icon in the Lokalise card to edit the details.
  4. Click on the Save button.

#Use Lokalise in your Hygraph project

As you create content, it will display in the Lokalise section of the Content editor, under App views. From there, you will be able to export content to Lokalise to be translated, then import those translations into Hygraph.

Finally, after the process has been completed, you will be able to view the translated content normally by accessing the Content editor.

Take into account that only localizable fields can be submitted to Lokalise. So the fields must be set as localized fields when added to the model.

Localized field checkboxLocalized field checkbox

You will find the Localized field checkbox at the bottom of the field details screen, which displays when you create or edit a field in the Schema editor.

#Export translation

Submit to translateSubmit to translate

  1. Navigate to the content editor.
  2. Select Lokalise under the App views section of the right sidebar.
  3. Use the checkboxes to select the desired content from the list, and send it to Lokalise by clicking on the Submit to Translate link at the top of the form.
  4. A pop-up will display, where you need to select the locales to export. Select the necessary checkboxes, and click on the Export translation button.
  5. The translation status will change to In progress, and you will be able to find the content ready to translate in your Lokalise account.

If the content is exported successfully, a green message will pop up in the lower right corner of the screen indicating this. If it fails, a red message will be displayed in the same place indicating that the submit was unsuccessful.

The following fields are supported to be exported to Lokalise:

  • Single-line text
  • Multi-line text
  • Markdown
  • Richtext
  • Slug

Export is also supported for Basic and Modular Components, but only for the supported field types.

#Import translation

After exporting content to Lokalise, it will be translated and saved there. You can then import that content back to Hygraph by following these steps:

Import translationImport translation

  1. Navigate to the Lokalise section of the Content editor. Use the checkboxes to select the entries that you want to import translations for, then click on the Import Translation link at the top of the form.
  2. A pop-up will display, where you need to select the language or languages of the content being imported. Select the necessary checkboxes, and click on the Import translation button. The translation status will change to Imported as a result.

The following fields are supported to be imported from Lokalise:

  • Single-line text
  • Multi-line text
  • Markdown
  • Richtext
  • Slug

Import is also supported for Basic and Modular Components, but only for the supported field types.

#Translation statuses

The Lokalise app view of the Content editor contains a form that allows you to view the localization status of your content as well as to export and import translations in bulk.

Lokalise secton in App viewLokalise secton in App view

Your Locale status refers to the default language in your project. The language will be indicated next to the column title, i.e. Locale status (en).

Your Global status refers to all the languages that were submitted for translation.

StatusDescription
MissingIndicates that an entry has never been sent to Lokalise.
In progressIndicates that an entry has been submitted for translation.
DoneIndicates that all translations have been finished in Lokalise, marked as reviewed, and imported.
ChangedIndicates that an entry has been edited after it was sent to Lokalise.
ImportedIndicates that one or more translations - but not all - have been finished in Lokalise, and imported to Hygraph.

#View translations

  1. Navigate to the content editor, and select the view of the model you included Lokalise in.
  2. Edit an entry that you imported a translation for by clicking on the pencil icon. The content will display at the center of the screen.
  3. You will find the Localizations section in the right sidebar. You have the following options:
    1. Click on the + icon to add a translation.
    2. Click on the trash icon to delete a translation.
    3. Click on the eye icon to view a translation in the editor.

View translationsView translations

#Troubleshooting

If the Content Editor displays the message This model has no localized fields under localizations in the sidebar, while the Schema Editor has localizations configured, go to Project settings > Locales. There, make sure your project has at least two languages configured.

Locales in project settingsLocales in project settings

If you have only one language configured there, select another language for localizations using the Display name dropdown, then click on Add.

#Resources