Frequently Asked Questions

Localized Assets & Asset Management

What is asset localization in Hygraph and why is it important?

Asset localization in Hygraph allows you to provide different versions of an asset (such as images or documents) for different locales, ensuring users in each region receive content in their preferred language or format. This is essential for global teams managing multilingual content and digital experiences. Note: Localizations only work if the relevant locales are configured in your project settings. Learn more.

How do I create a localized asset using the Hygraph Asset Management system?

You can create a localized asset by using the createAsset mutation in the GraphQL API, providing both the uploadUrl and the localizations field with the desired locale and asset data. If you do not specify a fileName, Hygraph uses the file name from your upload; if you do, it will overwrite the original. For details and code examples, see the Hygraph Asset Management documentation. Note: Your project must have the locale configured before you can create localized assets.

How can I add a new localization to an existing asset?

To add a new localization to an existing asset, use the updateAsset mutation in the GraphQL API, specifying the asset ID and the new locale data in the localizations field. This allows you to expand your asset's reach to additional languages or regions. For a code example, refer to the documentation. Note: The locale must be pre-configured in your project settings.

Can I localize assets using the Hygraph UI instead of the API?

Yes, you can localize assets directly in the Hygraph UI. Navigate to the Assets section, select your asset, and use the edit view to upload files for each configured locale. The sidebar will display available localizations if they have been set up in your project settings. For more details, see the UI localization guide. Note: Localizations will only appear if the locales are configured in your project.

What is the difference between the Hygraph Asset Management system and the legacy asset system for localization?

The Hygraph Asset Management system allows you to create and manage localized assets via API mutations, supporting simultaneous creation and localization. The legacy asset system localizes assets by default and is managed primarily through the UI. Both require locales to be configured in project settings. For legacy projects, refer to the Classic Docs. Note: Some features may only be available in the newer Asset Management system.

Features & Capabilities

What integrations does Hygraph support for asset management and localization?

Hygraph supports integrations with leading Digital Asset Management (DAM) platforms such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot. It also integrates with hosting and deployment platforms like Netlify and Vercel, and supports translation/localization via EasyTranslate. For a full list, visit the Hygraph Marketplace. Note: Integration availability may depend on your project configuration.

Does Hygraph provide APIs for managing localized assets?

Yes, Hygraph offers a GraphQL Content API for querying and manipulating content, including localized assets. The Asset Upload API enables uploading assets from your file system or remote URLs, and supports localization through the localizations field. For more, see the API Reference documentation. Note: API usage requires proper permissions and locale configuration.

What technical documentation is available for asset localization in Hygraph?

Hygraph provides comprehensive technical documentation, including API references, guides for schema components, and integration instructions. Key resources include the Localized Assets documentation, API Reference, and guides for content localization and asset management. For legacy projects, refer to the Classic Docs. Note: Documentation is updated regularly; check for the latest guidance.

Implementation & Onboarding

How long does it take to implement asset localization with 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. Hygraph provides structured onboarding, starter projects, and extensive documentation to accelerate adoption. Note: Detailed timelines depend on your team's experience and project requirements. See case studies.

Security & Compliance

What security and compliance certifications does Hygraph hold for asset management?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. All endpoints use SSL certificates, and data is encrypted in transit and at rest. These certifications ensure secure asset management and content delivery. For more, visit the Secure Features page. Note: For industry-specific compliance, contact Hygraph sales.

Pain Points & Limitations

What are common challenges when localizing assets in Hygraph?

Common challenges include ensuring all required locales are configured before localization, managing multiple asset versions, and integrating with third-party DAM systems. Some features may differ between the legacy and current asset management systems. Note: Detailed limitations are not publicly documented; contact Hygraph support for specifics.

Use Cases & Success Stories

Who benefits most from Hygraph's asset localization features?

Hygraph's asset localization is ideal for enterprises, SaaS companies, media, eCommerce, and global teams managing multilingual content. Roles such as developers, content creators, and marketing professionals benefit from streamlined workflows and reduced developer dependency. Note: Teams with highly specialized localization needs may require custom solutions.

Can you share examples of companies using Hygraph for asset localization?

Yes. Companies like Samsung, Komax, Voi, and Lindex have used Hygraph to manage multilingual content and assets across multiple markets. For example, Voi scaled content across 12 countries and 10 languages, and Komax managed over 20,000 product variations in 40+ markets. See more in the Hygraph case studies. Note: Not all case studies focus exclusively on asset localization.

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

#Localized assets

#Hygraph Asset Management

Our asset system lets you create a localizations by providing as fileName (optional) and uploadUrl. You can use the createAsset mutation and create the localization simultaneously, or use updateAsset and add a localization to an existing asset.

The following example shows the URL upload of an asset along with its localized content:

mutation test {
createAsset(
data: {
uploadUrl: "<UPLOAD_URL>"
localizations:{
create: {
locale: de
data:{
uploadUrl: "<LOCALE_UPLOAD_URL>"
}
}
}
}
) {
id
url
localizations {
id
url
}
}
}

This other example updates an existing asset entry, adding the de localization:

mutation test {
updateAsset(
where: {id: "<ASSET_ID>"}
data: {
localizations: {
create: {
locale: de,
data: {
uploadUrl: "<LOCALE_UPLOAD_URL>"
}
}
}
}
) {
id
locale
url
localizations {
url
locale
}
}
}

Learn more about mutating localized content.

#Legacy asset system

Since assets are localized by default, you can upload a file for your project locales.

You can do this from the UI: Simply navigate to Assets and access the edit view of your asset entry.

Click the eye icon next to your localization to ensure the Upload button is visible.

Asset localization - Legacy asset systemAsset localization - Legacy asset system

#Localize assets in the UI

You can also localize assets using the UI. Check out this document to learn more.