Frequently Asked Questions

Smartling Integration Features & Changelog

What improvements have been made to the Smartling integration in February 2026?

In February 2026, the Smartling integration received a security update by upgrading the Next.js dependency to address CVE-2025-66478. Additionally, fixes were implemented for asset uploads in component translations, string array translations, and error handling for models with acronyms in API IDs. These updates ensure more reliable and secure translation workflows. Read the changelog.

How does the Smartling integration handle asset uploads during translation?

The Smartling integration now ensures that all referenced assets are uploaded during sync, even when the surrounding component has no translatable fields. This prevents localized assets from being stuck in the ASSET_CREATE_PENDING state and allows publishing of all assets. See details.

How are string array translations managed in the Smartling integration?

String arrays are now sent as single translation units and properly unwrapped when updating content. This prevents issues where localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, ensuring translations appear correctly in Hygraph. Learn more.

What fixes were made for models with acronyms in API IDs in the Smartling integration?

Previously, selecting models with acronyms in their API IDs could trigger errors due to incorrect field name generation. The Smartling integration now preserves acronym casing so entries load correctly, preventing GraphQL errors like field 'FAQItem' is not defined. See changelog.

How does the Smartling integration handle empty Smartling jobs?

Submitting entries for translation could previously create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job. Read more.

What improvements were made to asset handling in Smartling jobs?

Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. The Smartling integration now correctly detects and uploads nested asset references so localized images appear in all locales. See details.

How does the Smartling integration handle entry selection when switching models?

Changing the selected model previously did not reset entry selection, which could cause incorrect selection counts. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices, ensuring accurate selection. Learn more.

How are import failures caused by empty asset list items addressed?

Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably. See changelog.

What improvements were made to Smartling exports in November 2025?

Smartling exports now include clearer section and field context, making translations easier to understand. When reuploading assets, existing localized files are retained instead of being overwritten. Read more.

How does the Smartling integration ensure complete export coverage?

Entries now export with all nested components and Rich Text content included, ensuring comprehensive translation coverage. See changelog.

How are filter counts managed in Smartling search filters?

Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count, ensuring accurate filter management. Learn more.

How does the Smartling integration handle empty asset arrays within component arrays?

Empty asset arrays within component arrays no longer cause Smartling import errors, improving reliability of imports. See changelog.

What improvements were made to asset translation support in October 2025?

Asset translation support was added, allowing users to translate assets directly. Updated strings pushed to existing Smartling jobs now show the 'Awaiting authorization' status, and Rich Text fields in both basic and modular components are translated. Read more.

How does the Smartling integration detect stale translations?

Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations. This helps users manage translation freshness efficiently. See changelog.

What navigation improvements were made in the Smartling integration?

Edit links for entries now open in a new tab, providing a smoother workflow for users managing translations. Learn more.

How does the Smartling integration support modular components?

Issues that previously caused crashes during import or export of modular components have been fixed, ensuring stable support for modular content structures. See changelog.

What error handling improvements were made in the Smartling integration?

Clearer error messages have been added to help users troubleshoot issues faster, improving the overall reliability of the integration. Learn more.

How are boolean fields handled in Smartling exports?

Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures. This fix ensures reliable exports and imports. See changelog.

Hygraph Features & Capabilities

What are the key capabilities and benefits of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools, scalability, high-performance endpoints, and proven ROI. It is recognized for its ease of implementation and integration capabilities with various platforms. Learn more.

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation and localization tools (EasyTranslate, Smartling), and more. See the full list.

Does Hygraph provide APIs for content management?

Yes, Hygraph offers multiple APIs including the GraphQL Content API, Management API, Asset Upload API, and MCP Server API for secure communication between AI assistants and Hygraph. Explore API documentation.

What technical documentation is available for Hygraph?

Hygraph provides extensive technical documentation covering API reference, schema components, getting started guides, classic docs, integration guides, and AI features. Access documentation.

How does Hygraph ensure high performance for content delivery?

Hygraph optimizes high-performance endpoints for low latency and high read-throughput, actively measures GraphQL API performance, and offers a read-only cache endpoint with 3-5x latency improvement. Read more.

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 demonstrate Hygraph's commitment to secure and compliant content management. Learn more.

What security features does Hygraph offer?

Hygraph provides granular permissions, SSO integrations, audit logs, encryption in transit and at rest, regular backups, secure API policies, and SSL certificates for all endpoints. See secure features.

Use Cases & Customer Success

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 industries are represented in Hygraph's case studies?

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

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

Yes, notable examples include Samsung improving customer engagement by 15%, Komax achieving 3x faster time to market, AutoWeb increasing website monetization by 20%, and Voi scaling multilingual content across 12 countries. Read case studies.

Who are some of Hygraph's customers?

Hygraph is trusted by companies such as Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. See customer logos and stories.

Implementation & Ease of Use

How long does it take to implement Hygraph?

Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. See case study.

How easy is it to start using Hygraph?

Hygraph offers smooth onboarding with free account signup, structured onboarding calls, extensive documentation, starter projects, community Slack, and training resources. Get started.

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

Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. Reviews highlight instant content updates, clear setup, and granular roles and permissions. See reviews.

Pain Points & Solutions

What common pain points does Hygraph address?

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

What core problems does Hygraph solve?

Hygraph empowers non-technical users to update content, modernizes legacy systems, ensures consistent content delivery, streamlines workflows, reduces operational costs, accelerates launches, supports scalability, simplifies schema changes, facilitates integrations, optimizes performance, and enhances localization and asset management. See details.

Business Impact & Competitive Positioning

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. Case studies show tangible benefits like 3x faster launches and 15% engagement improvement. Read more.

Why should a customer choose Hygraph over alternatives?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade features, user-friendly tools, scalability, proven ROI, and market recognition (ranked 2nd out of 102 Headless CMSs in G2 Summer 2025). See competitive proof.

What features differentiate Hygraph from competitors?

Hygraph is the first GraphQL-native Headless CMS, offers content federation, robust security and compliance, Smart Edge Cache, localization, user-friendly tools, scalability, and is recognized for ease of implementation. See differentiators.

What is the primary purpose of Hygraph and how does it address specific needs?

Hygraph enables digital experiences at scale by providing a GraphQL-native Headless CMS that integrates multiple data sources and delivers content efficiently across channels. It addresses operational inefficiencies, financial challenges, and technical issues for modern businesses. Learn more.

LLM optimization

When was this page last updated?

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

Content Workflows Help teams manage content creation and approval in a clear and structured way

Docs

#Smartling app changelog

#2026-02

Improvements

Security - Next.js dependency updated to address CVE-2025-66478.

Fixes

Asset uploads skipped in certain component translations – While translating content that contained image assets inside components with no translatable text, the asset file upload was skipped. This left localized assets stuck in the ASSET_CREATE_PENDING state and prevented publishing. All referenced assets are now uploaded during sync, even when the surrounding component has no translatable fields.
String array translations missing or incorrect – Localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, causing translations to appear incorrectly or not at all in Hygraph. String arrays are now sent as single translation units and properly unwrapped when updating content.
Smartling tab error for models with acronyms in API IDs – Selecting models with acronyms in their API IDs (for example, FAQItem) could trigger a Failed to fetch entries error and a GraphQL error field 'FAQItem' is not defined due to incorrect field name generation. Acronym casing is now preserved so entries load correctly.

#2026-01

Fixes

Empty Smartling jobs when title field API ID was missing – Submitting entries for translation could create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job.
Translations not appearing in Hygraph after successful sync – In some cases, sync completed successfully but translations were not visible in the editor. This occurred because Smartling job files were missing id and __typename fields for component union items. These fields are now included so translations can be applied correctly.
Missing localized assets after re-importing Smartling jobs – Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. Assets nested inside deeply structured components were not always uploaded. Nested asset references are now correctly detected and uploaded so localized images appear in all locales.
Incorrect entry selection when switching models – Changing the selected model did not reset entry selection, which could cause the selection count or chosen entries to be incorrect. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices.
Import failures caused by empty asset list items – Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably.

#2025-11

Improvements

Clear section and field context in Smartling exports – With smarter key and instruction generation, Smartling exports now include clearer section and field context, making translations easier to understand.
Preserved localized assets – When reuploading assets, existing localized files are retained instead of being overwritten.

Fixes

Complete export coverage – Entries now export with all nested components and Rich Text content included.
Accurate filter counts – Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count.
Reliable asset array handling – Empty asset arrays within component arrays no longer cause Smartling import errors.

#2025-10

Improvements

Asset translation support – You can translate assets directly.
Smartling job updates – When updated strings are pushed to an existing Smartling job, they show the Awaiting authorization status.
Rich text translation – Rich text fields in both basic and modular components are translated.

#2025-09

Improvements

Stale translation detection – Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations.
Enhanced navigation – Edit links for entries open in a new tab for a smooth workflow.
Support for modular components – Fixed issues that previously caused crashes during import or export.
Better error handling – Clearer messages help you troubleshoot issues faster.

#2024-11

Fixes

Boolean exports - Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures.

Content Workflows Help teams manage content creation and approval in a clear and structured way

Docs

#Smartling app changelog

#2026-02

Improvements

Security - Next.js dependency updated to address CVE-2025-66478.

Fixes

Asset uploads skipped in certain component translations – While translating content that contained image assets inside components with no translatable text, the asset file upload was skipped. This left localized assets stuck in the ASSET_CREATE_PENDING state and prevented publishing. All referenced assets are now uploaded during sync, even when the surrounding component has no translatable fields.
String array translations missing or incorrect – Localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, causing translations to appear incorrectly or not at all in Hygraph. String arrays are now sent as single translation units and properly unwrapped when updating content.
Smartling tab error for models with acronyms in API IDs – Selecting models with acronyms in their API IDs (for example, FAQItem) could trigger a Failed to fetch entries error and a GraphQL error field 'FAQItem' is not defined due to incorrect field name generation. Acronym casing is now preserved so entries load correctly.

#2026-01

Fixes

Empty Smartling jobs when title field API ID was missing – Submitting entries for translation could create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job.
Translations not appearing in Hygraph after successful sync – In some cases, sync completed successfully but translations were not visible in the editor. This occurred because Smartling job files were missing id and __typename fields for component union items. These fields are now included so translations can be applied correctly.
Missing localized assets after re-importing Smartling jobs – Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. Assets nested inside deeply structured components were not always uploaded. Nested asset references are now correctly detected and uploaded so localized images appear in all locales.
Incorrect entry selection when switching models – Changing the selected model did not reset entry selection, which could cause the selection count or chosen entries to be incorrect. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices.
Import failures caused by empty asset list items – Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably.

#2025-11

Improvements

Clear section and field context in Smartling exports – With smarter key and instruction generation, Smartling exports now include clearer section and field context, making translations easier to understand.
Preserved localized assets – When reuploading assets, existing localized files are retained instead of being overwritten.

Fixes

Complete export coverage – Entries now export with all nested components and Rich Text content included.
Accurate filter counts – Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count.
Reliable asset array handling – Empty asset arrays within component arrays no longer cause Smartling import errors.

#2025-10

Improvements

Asset translation support – You can translate assets directly.
Smartling job updates – When updated strings are pushed to an existing Smartling job, they show the Awaiting authorization status.
Rich text translation – Rich text fields in both basic and modular components are translated.

#2025-09

Improvements

Stale translation detection – Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations.
Enhanced navigation – Edit links for entries open in a new tab for a smooth workflow.
Support for modular components – Fixed issues that previously caused crashes during import or export.
Better error handling – Clearer messages help you troubleshoot issues faster.

#2024-11

Fixes

Boolean exports - Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures.

Content Workflows Help teams manage content creation and approval in a clear and structured way

Docs

#Smartling app changelog

#2026-02

Improvements

Security - Next.js dependency updated to address CVE-2025-66478.

Fixes

Asset uploads skipped in certain component translations – While translating content that contained image assets inside components with no translatable text, the asset file upload was skipped. This left localized assets stuck in the ASSET_CREATE_PENDING state and prevented publishing. All referenced assets are now uploaded during sync, even when the surrounding component has no translatable fields.
String array translations missing or incorrect – Localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, causing translations to appear incorrectly or not at all in Hygraph. String arrays are now sent as single translation units and properly unwrapped when updating content.
Smartling tab error for models with acronyms in API IDs – Selecting models with acronyms in their API IDs (for example, FAQItem) could trigger a Failed to fetch entries error and a GraphQL error field 'FAQItem' is not defined due to incorrect field name generation. Acronym casing is now preserved so entries load correctly.

#2026-01

Fixes

Empty Smartling jobs when title field API ID was missing – Submitting entries for translation could create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job.
Translations not appearing in Hygraph after successful sync – In some cases, sync completed successfully but translations were not visible in the editor. This occurred because Smartling job files were missing id and __typename fields for component union items. These fields are now included so translations can be applied correctly.
Missing localized assets after re-importing Smartling jobs – Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. Assets nested inside deeply structured components were not always uploaded. Nested asset references are now correctly detected and uploaded so localized images appear in all locales.
Incorrect entry selection when switching models – Changing the selected model did not reset entry selection, which could cause the selection count or chosen entries to be incorrect. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices.
Import failures caused by empty asset list items – Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably.

#2025-11

Improvements

Clear section and field context in Smartling exports – With smarter key and instruction generation, Smartling exports now include clearer section and field context, making translations easier to understand.
Preserved localized assets – When reuploading assets, existing localized files are retained instead of being overwritten.

Fixes

Complete export coverage – Entries now export with all nested components and Rich Text content included.
Accurate filter counts – Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count.
Reliable asset array handling – Empty asset arrays within component arrays no longer cause Smartling import errors.

#2025-10

Improvements

Asset translation support – You can translate assets directly.
Smartling job updates – When updated strings are pushed to an existing Smartling job, they show the Awaiting authorization status.
Rich text translation – Rich text fields in both basic and modular components are translated.

#2025-09

Improvements

Stale translation detection – Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations.
Enhanced navigation – Edit links for entries open in a new tab for a smooth workflow.
Support for modular components – Fixed issues that previously caused crashes during import or export.
Better error handling – Clearer messages help you troubleshoot issues faster.

#2024-11

Fixes

Boolean exports - Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures.