Dictionary manager

In this browser, using localStorage. Nothing is sent to a server, and there is no account. That also means your words don't follow you to another browser or device on their own, and you must use Export JSON to back up or move a dictionary, and Import a file to bring it back.

If your browser clears site data, unexported words are gone, so export anything you care about.

Exports use the same shape as the Tlag dictionary (conlangatucsd.com/tlag/data/dictionary.json), so a file from either tool opens in the other:

{
  "entries": [
    {
      "t": "cina",
      "en": "cat",
      "ipa": "[ɕi.næ]",
      "pos": "Noun",
      "ety": "a priori",
      "cats": ["organisms"],
      "ex": [{ "tlag": "...", "en": "...", "gloss": "..." }]
    }
  ]
}

Only t (word) and en (definition) are required; every other field is optional. A bare [...] array of such objects imports too.

A header row followed by one word per line:

word,definition,ipa,part_of_speech,etymology,categories,example_tlag,example_english,example_gloss
cina,cat,[ɕi.næ],Noun,a priori,organisms,,,

• Separate multiple categories with |, e.g. food and drink|organisms.
• Only the first example sentence per word round-trips through CSV; extra examples are kept in JSON exports.

Load Tlag sample imports the club language's live wordlist (the same data behind the Tlag gloss, fetched from the main site) as its own dictionary. Use it to see how a filled-in dictionary feels, or as example rows for your own CSV work. It never touches your other dictionaries.

Add ?w= plus the word to the address, e.g. ?w=cina. Opening that link filters the current dictionary to that word. (Which dictionary is "current" depends on the browser opening the link, since dictionaries live in local storage.)