The Transifex Web Editor provides a powerful set of filters to help you locate, review, and manage strings. Filters are accessible by clicking the search box above the strings list (or pressing Alt + S) and selecting from the available filter categories. Multiple filters can be combined using AND (&) and OR (|) logic.

Editor (Translation View)

How to Use Filters

Click the search box above the strings list, or press Alt + S, to open the filter panel.
Select a filter group (e.g., Text, Status, Tags) and then choose a sub-filter.
To search for an exact phrase, wrap your query in double quotes (e.g., "Contact Transifex").
Use * as a wildcard to match any value (e.g., in the Comment filter, * returns all strings that have any comment).
Remove a filter by clicking its removal icon in the search box, or by clearing it and pressing Enter.

Resource

Filter	Key	Type	Values
Resource	`resource`	Multi-select	Search by resource name

Resource — Filters strings to those belonging to one or more specific resources. This filter only appears when you are in the All Resources view (i.e., viewing strings across all resources in a project simultaneously). You can search by resource name and select multiple resources.

Text

These filters search the content of source strings and their translations.

Filter	Key	Type
Text	`text`	Text input
Text doesn't contain	`text_not_contains`	Text input
Translation text	`translation_text`	Text input
Translation text doesn't contain	`translation_text_not_contains`	Text input
Same source and translation	`same_source_and_translation`	Toggle

Text — Returns strings where the source string contains the specified text. Wrap your query in double quotes for an exact whole-word match.
Text doesn't contain — Returns strings where the source string does not contain the specified text. Useful for finding strings that have been missed or need a specific term added.
Translation text — Returns strings where the translation contains the specified text. Use this to audit how a term has been translated across your project.
Translation text doesn't contain — Returns strings where the translation does not contain the specified text. Useful for spotting translations that are missing a required term or variable.
Same source and translation — Returns strings where the translation is identical to the source string. This can help identify strings that may have been left untranslated or copied directly from the source.

Status

These filters narrow strings by their translation workflow status.

Filter	Key	Type	Values
Translated	`translated`	Yes / No	`yes`, `no`
Reviewed	`reviewed`	Yes / No	`yes`, `no`
Proofread	`proofread`	Yes / No	`yes`, `no`

Translated — Filters strings by whether they have a translation saved (yes) or are still untranslated (no).
Reviewed — Filters strings by whether their translation has been reviewed (yes or no).
Proofread — Filters strings by whether they have been through the second review (proofread) step (yes or no). Proofread strings display a double checkmark in the string list. This filter only appears when the project has the review step enabled in its Workflow settings.

📝Note: Untranslated strings will not appear when filtering for reviewed/proofread: yes.

Users

These filters allow you to find strings based on who translated or reviewed them.

Filter	Key	Type
Translator	`translator`	Multi-select (username search)
Translator is not	`translator_not`	Multi-select (username search)
Reviewer	`reviewer`	Multi-select (username search)
Reviewer is not	`reviewer_not`	Multi-select (username search)

Translator — Returns strings that were translated by the specified user(s). Search by username and select one or more collaborators.
Translator is not — Returns strings that were not translated by the specified user(s). Useful for finding strings that still need attention from a specific team member.
Reviewer — Returns strings whose translation was reviewed by the specified user(s).
Reviewer is not — Returns strings whose translation was not reviewed by the specified user(s).

Date

All date filters accept values in YYYY-MM-DD format.

Filter	Key	Type
Translated before	`translated_before`	Date
Translated after	`translated_after`	Date
Reviewed before	`reviewed_before`	Date
Reviewed after	`reviewed_after`	Date
Source updated before	`source_updated_before`	Date
Source updated after	`source_updated_after`	Date

Translated before — Returns strings whose translation was last saved before the specified date.
Translated after — Returns strings whose translation was last saved after the specified date.
Reviewed before — Returns strings whose translation was last reviewed before the specified date.
Reviewed after — Returns strings whose translation was last reviewed after the specified date.
Source updated before — Returns strings whose source content was last updated before the specified date.
Source updated after — Returns strings whose source content was last updated after the specified date.

Label

These filters are related to issues, translation quality checks, and string metadata.

Filter	Key	Type	Values
Issue	`issue`	Single-select	`open`, `resolved`, `none`
Issue category	`issues_category`	Single-select	Category names
Issue priority	`issues_priority`	Single-select	Priority levels
Translation checks	`check`	Single-select	`all`, `error`, `warning`, `none`
Translation check type	`check_type`	Single-select	`glossary`, `custom_placeholder`
Pluralized	`pluralized`	Yes / No	`yes`, `no`
Screenshot	`screenshot`	Yes / No	`yes`, `no`

Issue — Filters strings by the status of any attached issue: open (has an unresolved issue), resolved (issue has been addressed), or none (no issues attached). Issues are threaded discussions attached to individual strings.
Issue category — Filters strings by the category of their issue (e.g., "Mistranslation", "Suggestion"). Only available when issue categories have been configured for the organisation. The available categories depend on your organisation's setup.
Issue priority — Filters strings by the priority level of their attached issue. The available priority levels depend on your organisation's configuration.
Translation checks — Filters strings by the result of automated translation quality checks. all returns any string with a check result, error returns strings with failing checks that must be fixed before saving, warning returns strings with check warnings that can be saved despite the issue, and none returns strings with no check results.
Translation check type — Filters strings by the type of translation check that has flagged them: glossary (the translation does not respect a glossary term) or custom_placeholder (a required variable or placeholder is missing or modified in the translation).
Pluralized — Filters strings that have plural forms defined (yes) or do not (no). Plural strings require separate translations for each plural rule in the target language.
Screenshot — Filters strings by whether they are mapped to a screenshot for visual context (yes or no). Screenshots help translators understand the UI context of a string.

Branch

These filters are only available when viewing a child branch resource (i.e., a resource created via Transifex's branching feature).

Filter	Key	Type	Values
Common branch strings	`common_branch_strings`	Yes / No	`yes`, `no`
Branch state	`branch_state`	Multi-select	`AHEAD`, `CONFLICT`, `RESOLVED`, `DIVERGED SOURCE`

Common branch strings — Filters strings that exist in both the parent and child branch (yes), or strings unique to the child branch (no).
Branch state — Filters strings by their synchronisation state relative to the parent branch:
- AHEAD — The child branch has translations not yet present in the parent. This includes strings with child-only translations, updated translations since the last sync, or reviewed strings not yet reviewed in the parent.
- CONFLICT — The parent and child have competing translations or review statuses (e.g., both were edited independently, or review states differ).
- RESOLVED — A conflict between parent and child that was resolved via the Editor.
- DIVERGED SOURCE — The source string has been updated in one branch but not the other, causing the source text to differ between parent and child.

In the source language view, only the DIVERGED SOURCE state is available.

More Filters

Additional filters are grouped under the More category.

TM Fill-up Leverage

Filter	Key	Type
TM fill-up leverage ≥	`tm_fillup_leverage_gte`	Numeric input
TM fill-up leverage ≤	`tm_fillup_leverage_lte`	Numeric input

TM fill-up leverage ≥ — Returns strings whose Translation Memory fill-up match score is greater than or equal to the specified percentage. This lets you find strings that were filled in with high-confidence TM matches.
TM fill-up leverage ≤ — Returns strings whose TM fill-up match score is less than or equal to the specified percentage. The accepted range for fuzzy TM fill-up is 85–101%, where 100% represents a perfect match and 101% represents a context-aware match.

Translation Quality Index (TQI)

These filters are only available on projects where TQI has been enabled.

Filter	Key	Type
TQI ≥	`tqi_gte`	Numeric input (0.00 - 1.00)
TQI ≤	`tqi_lte`	Numeric input (0.00 - 1.00)

TQI ≥ — Returns strings with a Translation Quality Index score greater than or equal to the specified value. The TQI measures the overall quality of a translation based on AI analysis.
TQI ≤ — Returns strings with a TQI score less than or equal to the specified value. Use this in combination with TQI ≥ to target a specific quality score range.

Key

Filter	Key	Type
Key	`key`	Text input
Key doesn't contain	`key_not_contains`	Text input

Key — Filters strings by their string key (the unique identifier used to reference the string in code, e.g., homepage.hero.title). Supports partial matching.
Key doesn't contain — Returns strings whose key does not contain the specified value.

Occurrence

Filter	Key	Type
Occurrence	`occurrence`	Text input

Occurrence — Filters strings by their recorded occurrence, typically the file path and/or line number where the string is defined in the source code (e.g., src/components/Header.jsx:42). This is useful for finding all strings that originate from a specific file. Supported by formats like .ts and .xliff.

Developer Notes

Filter	Key	Type
Developer notes	`developer_notes`	Text input

Developer notes — Filters strings that contain specific content in their developer notes field. Developer notes are added by developers to provide guidance to translators. Use * to return all strings that have any developer notes. Supports whole-word matching (wrap in double quotes) and wildcard (*).

Context

Filter	Key	Type
Context	`context`	Text input

Context — Filters strings by their context field. Context is a metadata field that can disambiguate strings with the same source text (e.g., the word "Post" used as a noun vs. a verb). Supports partial matching.

Origin

Filter	Key	Type	Values
Origin	`origin`	Single-select	See below

Origin — Filters strings by how their current translation was created or last updated. The available origin values are:

Value	Description
`AI:TRANSIFEX`	Translated using Transifex AI (the native AI translation feature)
`API`	Translation was submitted via the Transifex API
`EDITOR`	Translation was entered manually in the Transifex Web Editor
`MT:TRANSIFEX`	Translated using Transifex's Machine Translation add-on
`MT:GOOGLE`	Translated using the Google Translate MT engine
`MT:MICROSOFT`	Translated using the Microsoft Translator MT engine
`MT:AMAZON`	Translated using the Amazon Translate MT engine
`MT:ALEXA`	Translated using the Alexa MT engine
`MT:INTENTO`	Translated using the Intento MT engine
`MT:DEEPL`	Translated using the DeepL MT engine
`MT:DEEPL:DEFAULT`	DeepL translation using the default formality setting
`MT:DEEPL:LESS`	DeepL translation using the "less formal" formality setting
`MT:DEEPL:MORE`	DeepL translation using the "more formal" formality setting
`MT:CUSTOMMT`	Translated using the Custom.MT engine
`TM`	Translation was applied by the Translation Memory
`UPLOAD`	Translation was uploaded via a file upload
`VENDORS:E2F`	Translation was submitted by E2F (partnered vendor)
`VENDORS:GENGO`	Translation was submitted by Gengo (partnered vendor)
`VENDORS:TEXTMASTER`	Translation was submitted by TextMaster (partnered vendor)
`TX:AUTOMATED`	Translation was applied automatically by Transifex (e.g., via an automated workflow rule)
`TX:PROPAGATED`	Translation was propagated from another string with the same source text
`TX:MERGED`	Translation was applied as part of a branch merge operation

Comment

Filter	Key	Type
Comment	`comment`	Text input

Comment — Filters strings by the content of their comments. Use a keyword to find strings with comments containing that term, or use * to return all strings that have any comment.

Instructions

Filter	Key	Type
Instructions	`instructions`	Text input

Instructions — Filters strings by the content of their translator instructions. Instructions are notes attached to a string to guide translators (e.g., tone guidance, formatting rules). Supports partial matching and wildcard (*).

User Suggestions

Filter	Key	Type	Values
User suggestions	`user_suggestions`	Yes / No	`yes`, `no`

User suggestions — Filters strings that have translator-submitted suggestions (yes) or do not (no). Suggestions are alternative translations submitted by community translators and can be voted on. This filter helps reviewers and maintainers identify strings with community input awaiting review.

Tasks — Assigned To

Filter	Key	Type	Values
Exclusive tasks assigned to	`exclusive_tasks_assigned_to`	Single-select	`me`, `all`, `none`
Non-exclusive tasks assigned to	`non_exclusive_tasks_assigned_to`	Single-select	`me`, `all`, `none`

Both filters accept the same three values: Assigned to me, Assigned to anyone, and Unassigned.

Exclusive tasks assigned to — Filters strings that are part of an exclusive task (a task that locks the string for a specific assignee) based on their assignment status. Use "Assigned to me" to see only strings in your exclusive tasks, "Assigned to anyone" for all assigned strings, or "Unassigned" for strings not yet in any exclusive task.
Non-exclusive tasks assigned to — Filters strings that are part of a non-exclusive task (a task where anyone can contribute) based on their assignment status. Supports the same values as the exclusive tasks filter.

Repeated Strings

Filter	Key	Type	Values
Repeated strings	`repeated_strings`	Yes / No	`yes`, `no`

Repeated strings — Filters strings that share identical source text with strings in other resources (yes), or strings that are unique (no). This helps identify strings where a translation change in one resource could be propagated to others.

Live URL Path Filters

These filters are only available for Transifex Live projects. All path values should be entered without the domain (e.g., /pricing rather than https://example.com/pricing).

Filter	Key	Type
Live URL path starts with	`live_url_path_starts_with`	Text input
Live URL path doesn't start with	`live_url_path_not_starts_with`	Text input
Live URL path contains	`live_url_path_contains`	Text input
Live URL path doesn't contain	`live_url_path_not_contains`	Text input
Live URL path matches	`live_url_path_matches`	Text input
Live on page strings	`live_on_page_strings`	Single-select

Live URL path starts with — Returns strings that appear on pages whose URL path starts with the specified value (e.g., /blog to find all strings on blog pages).
Live URL path doesn't start with — Returns strings that appear on pages whose URL path does not start with the specified value.
Live URL path contains — Returns strings that appear on pages whose URL path contains the specified value (e.g., /product/ to match any product page).
Live URL path doesn't contain — Returns strings that appear on pages whose URL path does not contain the specified value.
Live URL path matches — Returns strings that appear on pages whose URL path exactly matches the specified value.
Live on page strings — Filters strings based on whether they are currently visible on a live page:
- on_page — Returns strings that are currently detected as active/present on a live page.
- not_on_page — Returns strings that are not currently detected on any live page.

Editor (Source View)

When you open the editor in the source language view, a different set of filters is available, focused on source string activity rather than translation status.

Text

Same as the default view: Text (text) and Text doesn't contain (text_not_contains).

Editor Activity (Status)

Filter	Key	Type	Values
Edited source string	`edited_source_string`	Yes / No	`yes`, `no`
Editor added source strings	`editor_added_source_strings`	Yes / No	`yes`, `no`

Edited source string — Filters for strings whose source text has been edited directly in the Transifex Editor (yes) or has not been edited this way (no).
Editor added source strings — Filters for source strings that were created directly in the Editor (yes) rather than uploaded via a file or API (no). This filter only appears when the "add source strings in editor" feature is enabled for the project.

Tags, Date, Label, Branch

The Tags, Date, Label, and Branch filter groups behave the same as in the default translation view, with the following differences:

Date only shows source_updated_before and source_updated_after (no translation date filters).
Label shows only issue, issues_category (if configured), issues_priority, pluralized, and screenshot (no translation check filters).

More (Source View)

Filter	Key	Type
Key	`key`	Text input
Key doesn't contain	`key_not_contains`	Text input
Occurrence	`occurrence`	Text input
Developer notes	`developer_notes`	Text input
Context	`context`	Text input
Origin (source)	`origin`	Single-select
Comment	`comment`	Text input

Origin (source view) — In the source language view, the Origin filter reflects how the source string was added to Transifex (not the translation origin). The available values are:

Value	Description
`API`	Source string was pushed via the Transifex API
`EDITOR`	Source string was created manually in the Transifex Editor
`UPLOAD`	Source string was added via a file upload
`AUTOFETCH`	Source string was automatically fetched from an integration .

Glossary Editor Filters

The Glossary Editor has its own set of filters for browsing glossary terms and their translations. All these filters have matches in the previous two views, so if you need more details, please refer to their respective sections.

Translation view (Glossary)

Group	Filters available
Text	`text`, `text_not_contains`, `translation_text`, `translation_text_not_contains`
Status	`translated`, `reviewed`
Tags	`tags`, `tags_not_contains`
Users	`translator`, `translator_not`, `reviewer`, `reviewer_not`
Date	`translated_before`, `translated_after`, `reviewed_before`, `reviewed_after`, `source_updated_before`, `source_updated_after`

Source view (Glossary)

Group	Filters available
Text	`text`, `text_not_contains`
Tags	`tags`, `tags_not_contains`
Date	`source_updated_before`, `source_updated_after`

Sorting Options

In addition to filters, strings can be sorted using the sort control in the editor. Sorting and filtering can be used together. Available sort options vary by view:

Translation view: