Skip to content
NSNormandin SystemsTHE EVERYDAY TOOLBOXMain site
{ }

Data / YOUR EVERYDAY TOOLBOX

ISO 639 Searcher

Search in ISO 639-1/2T/2B/3 language codes

✓ Free to use✓ No account neededHow to use this tool ↓
YOUR WORKSPACESee an example ↗

Opening your tool…

Runs in your browser. Check important results and keep a copy of your original files.

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from ISO 639 Searcher

ISO 639 Searcher makes it easier to look up language codes without scanning a long reference list manually. The reference exposes language-code systems such as ISO 639-1, 639-2 terminology and bibliographic forms, and ISO 639-3. Start with a specific name, code, or distinctive term, then compare the returned entry with the exact field your application expects. Choose the exact ISO 639 column requested by your dataset; not every language has a two-letter code. A lookup is most useful when you record both the displayed value and the convention behind it, since similar-looking labels can represent different kinds of information. A language code alone is not a complete locale. Region and script distinctions may require a language tag rather than a bare ISO code. Use the example below as a starting point and narrow the search if several entries look plausible. Before reusing a result, check that the selected entry matches the intended context rather than choosing only the first familiar-looking label.

Guide updated October 13, 2026

How to use this tool

  1. Enter a name, code, or keyword relevant to language codes. Use a distinctive term to avoid an unnecessarily broad result list.
  2. Review the returned entries and their labels. Choose the exact ISO 639 column requested by your dataset; not every language has a two-letter code.
  3. Compare the selected entry with the original source or the requirements of the receiving application. Similar names do not always mean interchangeable values.
  4. Copy the required field together with its context. A language code alone is not a complete locale. Region and script distinctions may require a language tag rather than a bare ISO code.

SEE IT IN PRACTICE

A worked example

EXAMPLE INPUT
French
RESULT / WHAT TO EXPECT
fr; fra; fre in the relevant code systems

French illustrates why three-letter terminology and bibliographic codes can differ, while the two-letter form is fr.

Language, script, and region

A language can be written in different scripts or used in different regional conventions. A bare language code identifies only one part of that context. For localization, distinguish content language from formatting locale and from a user’s location. Inspect whether the destination expects a two-letter code, a three-letter code, or a fuller language tag with additional subtags.

Terminology and bibliographic forms

Some languages have different three-letter terminology and bibliographic codes, such as fra and fre for French. Both can be legitimate in the relevant code system, so a mismatch is not automatically a typo. Read the ISO 639 column requested by the consumer. Preserve the code-system label in a migration plan instead of replacing one familiar three-letter value with another without checking downstream requirements.

When this tool is useful

  • Prepare language metadata with a clear reference convention.
  • Compare language-code systems by comparing the available fields.
  • Investigate localization labels using a reproducible search term.

Tips for a better result

  • A language code alone is not a complete locale. Region and script distinctions may require a language tag rather than a bare ISO code.
  • Choose the exact ISO 639 column requested by your dataset; not every language has a two-letter code.
  • Keep the original label alongside the selected code or reference while preparing an import. This makes mismatches easier to investigate later.

Frequently asked questions

Is en-US an ISO 639 code?

The en component is a language code, while en-US is a language tag containing a region subtag as well. A locale or language tag can convey information that a language code alone does not.

Why can several results appear relevant?

A short search term can match different names, identifiers, or descriptions. Read the full entry and the meaning of the requested field before selecting a value; similarity in spelling is not a reliable equivalence test.

How should I check the value before using it?

Match the result to the receiving system’s expected convention. Choose the exact ISO 639 column requested by your dataset; not every language has a two-letter code. For decisions that depend on current authoritative data, verify against the relevant primary reference rather than assuming a bundled list updates automatically.

What happens to the information I enter?

The utility processes your input in this browser. Some tools retain field values in browser storage or the URL; avoid entering secrets in shareable fields. Page and asset requests still go to the hosting provider. Read the privacy and offline-use notes for details.