---
title: >-
  New translatable boolean field for Metafield GraphQL Object - Shopify
  developer changelog
description: >-
  Shopify’s developer changelog documents all changes to Shopify’s platform.
  Find the latest news and learn about new platform opportunities.
source_url:
  html: 'https://shopify.dev/changelog/is-translatable-metafield-field'
  md: 'https://shopify.dev/changelog/is-translatable-metafield-field.md'
metadata:
  effectiveApiVersion: 2026-10
  affectedApi:
    - displayName: Admin GraphQL API
      handle: admin-graphql
  primaryTag:
    displayName: API
    handle: api
  secondaryTag:
    displayName: New
    handle: new
  indicatesActionRequired: false
  createdAt: '2026-09-09T15:55:21-04:00'
  postedAt: '2026-09-21T12:00:00-04:00'
  updatedAt: '2026-09-19T11:16:14-04:00'
  effectiveAt: '2026-09-21T12:00:00-04:00'
---

September 21, 2026

# New translatable boolean field for Metafield GraphQL Object

DateSeptember 21, 2026

Version[2026-10](https://shopify.dev/changelog?api_version=2026-10)

FlagsNew

SurfacesAPI

Affected APIs[Admin GraphQL API](https://shopify.dev/changelog?api_type=admin-graphql)

API version `2026-10` adds a non-null `translatable` field to the `Metafield` object in the GraphQL Admin API. Apps that fetch translatable metafields and migrate to `2026-10` can now see whether a metafield’s value is translatable directly on the metafield itself. If your app doesn’t query for translatable metafields by shop, you don’t need to change anything.

## What changed

The [`Metafield` object in the GraphQL Admin API](https://shopify.dev/docs/api/admin-graphql/2026-10/objects/Metafield) exposes a new non-null field, `translatable: Boolean!`, in API version `2026-10`:

```graphql
{
   product(id: "gid://shopify/Product/1") {
		metafield(namespace: "custom", key: "care_guide") {
			type          # "single_line_text_field"
			translatable  # true
		}
	}
}
```

`translatable` returns the result that the platform already enforces when it decides whether a metafield’s value can be translated.

Before this change, apps had to use the deprecated `TranslatableResourceType.METAFIELD` enum on `translatableResources` to query for translatable metafields. On API version `2026-10` and later, you should read `translatable` on the `Metafield` object instead of querying metafields through `translatableResources`.

## Who's affected

This applies to apps that:

* Call the GraphQL Admin API on version `2026-10` or later, and
* Fetch translatable metafields

Apps on version `2026-07` and earlier are unaffected. `translatable` isn’t available on those versions, and `TranslatableResourceType.METAFIELD` continues to exist there as deprecated.

Apps that read metafield values without regard to translatability are unaffected on every version.

This change introduces no feature preview and no new access scope. Availability depends only on the API version, so the field appears as soon as you move a request to `2026-10`.

## Why this matters

Apps need to move away from using the `TranslatableResourceType.METAFIELD` enum on `translatableResources` to fetch translatable metafields.

Before this change, deciding whether a metafield can be translated required a list of which metafield types are translatable. Apps also had to keep that logic in sync with the platform.

`translatable` collapses those rules into one boolean. Because the field resolves from the platform’s own predicate rather than a copy of the rules in your app, it stays correct when translatability rules change.

## What to do

If your app doesn’t look up translatable metafields by shop, you don’t need to change anything when you migrate to `2026-10`.

If it does, then when you migrate to `2026-10`:

1. Check whether you call `translatableResources` with `TranslatableResourceType.METAFIELD` in the top-level `resourceType` argument.

2. Update those queries to read the `translatable` field directly on `Metafield` objects instead of classifying metafields through `translatableResources`.

3. Test your changes on a development store using API version `2026-10` and confirm that:

   * Queries that previously passed `TranslatableResourceType.METAFIELD` no longer runs in your app, and
   * Your UI uses the `metafield.translatable` value to decide when to offer translation.

For a worked migration example, see the guide on [migrating metafield translation logic from `TranslatableResourceType.METAFIELD` to `Metafield.translatable`](https://shopify.dev/docs/apps/build/markets/migrate-translatable-metafields).

## Related docs

* [`translatableResources` query](https://shopify.dev/docs/api/admin-graphql/2026-10/queries/translatableResources)
* [`TranslatableResourceType` enum](https://shopify.dev/docs/api/admin-graphql/2026-10/enums/TranslatableResourceType)
* [API versioning for Shopify APIs](https://shopify.dev/docs/api/usage/versioning)
* [Custom data in Shopify apps](https://shopify.dev/docs/apps/build/custom-data)