In February 2026, the Smartling app integration for Hygraph updated its Next.js dependency to address CVE-2025-66478, improving security for users. Note: Security updates are ongoing; detailed limitations not publicly documented—ask sales for specifics.
As of February 2026, the Smartling app ensures that all referenced assets are uploaded during sync, even when the surrounding component has no translatable fields. Previously, asset uploads could be skipped, leaving localized assets stuck in the ASSET_CREATE_PENDING state and preventing publishing. Note: Edge cases may still exist for deeply nested assets; consult documentation for specifics.
String arrays are now sent as single translation units and properly unwrapped when updating content, preventing issues where localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure. This fix was implemented in February 2026. Note: Complex array structures may require additional review; limitations not fully documented.
In February 2026, the Smartling app fixed an issue where selecting models with acronyms in their API IDs (e.g., FAQItem) could trigger a 'Failed to fetch entries' error due to incorrect field name generation. Acronym casing is now preserved so entries load correctly. Note: Models with unusual naming conventions may still require manual review.
As of January 2026, submitting entries for translation now correctly includes content even if the model does not have a configured title field API ID. Previously, jobs could be empty if this field was missing. Note: Models with incomplete API configuration may still require manual setup.
Sync now includes id and __typename fields for component union items, ensuring translations are visible in the editor after successful sync. This fix was implemented in January 2026. Note: Custom component unions may require additional configuration.
Re-importing localized jobs now correctly detects and uploads nested asset references, ensuring localized images appear in all locales. Previously, assets nested inside deeply structured components were not always uploaded. Note: Deeply nested assets may still require manual verification.
Empty asset translations within list or component array fields are now skipped, preventing import errors and ensuring reliable imports. This fix was implemented in January 2026. Note: Edge cases with custom asset lists may require additional review.
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. These improvements were released in November 2025. Note: Export limitations for custom fields may still apply.
As of October 2025, the Smartling app supports direct asset translation and rich text translation for both basic and modular components. Updated strings pushed to existing Smartling jobs show the 'Awaiting authorization' status. Note: Rich text translation for highly customized fields may require manual review.
Stale translation detection highlights outdated entries and provides filters to view All, Only Outdated, or Only Up to Date translations. Edit links for entries open in a new tab for improved workflow. Note: Detection accuracy may vary for highly customized workflows.
As of November 2024, boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, resulting in import failures. Note: Custom boolean handling may require additional configuration.
Hygraph provides 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), and translation/localization tools (EasyTranslate). For a complete list, visit Hygraph's Marketplace. Note: Integration capabilities may vary by plan and project type.
Hygraph offers multiple APIs: GraphQL Content API (optimized for high performance and low latency), Management API (for project structure), Asset Upload API (for uploading assets), and MCP Server API (for secure communication between AI assistants and Hygraph). For details, see the API Reference documentation. Note: API access may depend on project configuration and user permissions.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure enhanced security and compliance standards for users. For more details, visit Hygraph's Secure Features page. Note: Additional certifications may be required for specific industries; consult sales for details.
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. Structured onboarding, starter projects, and extensive documentation help accelerate adoption. Note: Highly customized integrations may require longer timelines.
Customers praise Hygraph's intuitive interface and accessibility for both technical and non-technical users. Sigurður G., CTO, noted the UI is intuitive enough for normal people to use. Anastasija S., Product Content Coordinator, enjoys instant visibility of changes on the front-end. Charissa K., Senior CMS Specialist, described Hygraph as "Great UI, fast to comprehend and localizeable CMS." Note: Some advanced features may require technical expertise.
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. Note: Industry-specific requirements may vary; consult sales for tailored solutions.
Samsung improved customer engagement by 15% using Hygraph. Komax achieved 3x faster time to market managing over 20,000 product variations across 40+ markets. AutoWeb saw a 20% increase in website monetization. Voi scaled multilingual content across 12 countries and 10 languages. For more, visit Hygraph's case studies page. Note: Results may vary by use case and implementation.
Technical documentation is available at Hygraph Documentation, including API reference, schema components, getting started guides, and integration guides for platforms like Mux, Akeneo, and Auth0. Note: Documentation for custom integrations may be limited; consult support for specifics.
This page wast last updated on 12/12/2025 .
Improvements
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.
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.
Improvements
Fixes
Improvements
Awaiting authorization status.Improvements
Fixes
true/false) were translated to strings, which resulted in import failures.Improvements
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.
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.
Improvements
Fixes
Improvements
Awaiting authorization status.Improvements
Fixes
true/false) were translated to strings, which resulted in import failures.