---
title: More flexible translation export filters
date: 2026-05-21
description: Filter translation exports by metafield namespace, pick multiple languages or markets in one row, and combine base translations with market overrides.
tags: ["Exports"]
categories: ["Changelog"]
url: https://www.getaltera.com/changelog/2026-05-21-translation-export-filters/
---


We've refreshed the filters for translations exports. Picking multiple languages or markets no longer requires a row per value, and you can now scope an export to specific metafields without sifting through everything else.

### What's New

- **Metafield namespace.key filter** - export only translations for specific metafields by `namespace.key` (e.g. `custom.care_instructions, custom.size`).
- **Metafield namespace filter** - export every translation under a namespace at once (e.g. all `custom.*` keys) without listing each key.
- **Base translation token** - the market filter now has a **Base translation** option that brings non-market-scoped translations into the export alongside any markets you pick.

### Improvements

- **Language filter is now multi-select** - pick several languages in one filter row instead of adding a row per locale.
- **Market filter is now multi-select** - combine real markets, "All Markets", and "Base translation" in a single row.
- **Saved exports are auto-upgraded** - old exports with multiple `Language is equal to ...` rows are merged into the new multi-select shape on load. CLI scripts and saved API payloads using the old single-value form continue to work unchanged.
- **Empty exports avoided when only "Base translation" is picked** - the primary language is no longer pulled in unless a real market is being iterated.

See the [translations reference](https://support.getaltera.com/en/articles/13177878-translation-fields#export-filters) for the full list of available filters.