vtex-io-messages-and-i18n

You can localize VTEX IO apps by replacing hardcoded UI text with vtex.messages-backed copy, defining app-scoped message IDs in a messages context, and managing translation payloads in /messages/*.json files for each locale.

The best way to structure VTEX translation files is maintaining small, locale-specific /messages/*.json payloads explicitly declared in messages context, ensuring strict separation from configuration or secrets to keep UI strings discoverable and resolvable.

You need to use react-intl with vtex.messages when adding or refactoring localized storefront or Admin flows that display translated labels, buttons, headings, or alerts, ensuring user-facing strings come from the messages infrastructure.

Yes, vtex.messages can be used from backend or GraphQL boundaries to handle localized responses, provided you define stable, app-scoped message IDs and back them with the appropriate /messages/*.json payloads for each locale.

Translation keys should be kept separate from configuration in VTEX apps because message files are designed strictly for localized UI copy, and mixing them with secrets or configuration violates internationalization guardrails and makes translation reviews painful.