CLI Projects: Create, Sync and Archive

Commands

`babelize projects list`

List all your projects.

babelize projects list
babelize projects list --archived   # Include archived projects
babelize projects list --json       # Raw JSON output

`babelize projects get <id>`

Get full details of a single project.

babelize projects get <project-uuid>

`babelize projects create`

Create a new project (interactive prompts if flags not provided).

babelize projects create
babelize projects create \
  --name "My App" \
  --repo-url https://github.com/myorg/myapp \
  --branch main \
  --languages es,fr,de

The interactive flow asks for a source type (github or zip). For ZIP projects, run babelize init --source zip from inside the project directory. It zips the project, uploads the archive the same way the dashboard's Upload ZIP does, and creates the project from the uploaded copy. Anything in .gitignore is left out, whether or not the directory is a git repository. Some things are always left out:

dependencies, caches and build output: node_modules, .git, .next, .turbo, .venv, venv, vendor, __pycache__, and root-level dist, build and coverage
the local .babelize/local/report.json
secrets, even when git tracks them: .env and .env.* files (templates such as .env.example, .env.sample and .env.template are kept), *.pem, *.key, *.p12, *.pfx, *.keystore, SSH keys (id_rsa*, id_ed25519*), .npmrc, .pypirc, .netrc, a .yarnrc.yml that contains registry credentials, credentials.json, service-account*.json, and anything under .aws/, .ssh/ or .gcloud/

The CLI lists any secret files it skipped. The upload limit is 50 MB, and the CLI checks the size before it uploads. Only the account that uploaded an archive can create a project from it.

You don't need a ZIP project to translate locally. babelize translate runs on your machine and uploads nothing.

`babelize projects update <id>`

Update project settings.

babelize projects update <id> --name "New Name"
babelize projects update <id> --branch develop

`babelize projects delete <id>`

Delete a project (owner role required). Asks for confirmation.

babelize projects delete <id>
babelize projects delete <id> --yes  # Skip confirmation

`babelize projects sync <id>`

Sync the project with its remote GitHub repository.

babelize projects sync <id>

`babelize projects repo-status <id>`

Check if the project's repository is in sync with the remote.

babelize projects repo-status <id>

`babelize projects check-repo`

Test if a GitHub repository URL is accessible with current credentials.

babelize projects check-repo --url https://github.com/myorg/myapp

`babelize projects insights <id>`

Get translation insights (key counts, coverage).

babelize projects insights <id>

`babelize projects metadata <id>`

Get project metadata (framework detection, settings).

babelize projects metadata <id>

`babelize projects download <id>`

Download the generated locale files as a ZIP archive.

babelize projects download <id>
babelize projects download <id> --output ./my-locales.zip

Archive Management

babelize projects archive <id>       # Soft-archive a project
babelize projects unarchive <id>     # Restore archived project
babelize projects unfreeze <id>      # Unfreeze (if frozen by plan limit)

`babelize projects github-app-url`

Get the GitHub App installation URL (for connecting repos).

babelize projects github-app-url

`babelize projects brand-voice <id>`

Get the project's brand voice, or set it with --voice.

babelize projects brand-voice <id>                        # Show current voice
babelize projects brand-voice <id> --voice "friendly and concise"   # Set it

Languages

babelize languages list                          # All system languages
babelize languages get <languageId>
babelize languages project-list <projectId>      # Languages on a project
babelize languages add <projectId> <languageId>
babelize languages remove <projectId> <languageId>
babelize languages codes                         # ISO ↔ FLORES-200 code table
babelize languages codes --rtl                   # RTL languages only
babelize languages check <isoCode>               # Is this ISO code valid?
babelize languages to-flores <isoCode>           # ISO-639-1 → FLORES-200
babelize languages from-flores <floresCode>      # FLORES-200 → ISO-639-1

Team Members

babelize members list <projectId>
babelize members add <projectId> --user <user-id> --role editor
babelize members update <projectId> <userId> --role viewer
babelize members remove <projectId> <userId>
babelize members transfer <projectId> --user <new-owner-id>

members add takes an existing user ID, not an email, and only re-adds someone who has already accepted an invitation to this project: nobody is put on a team without agreeing to it. New teammates are invited by email with babelize invitations send <projectId> --email user@example.com --role editor and join when they accept. Roles are admin, editor and viewer; ownership moves only with members transfer.

Translation Memory

Translation memory is owned by the project owner and shared across all of their projects. The <projectId> argument selects which project's API route to call — it does not limit the results: owners list, export, and manage their entire memory, while members are limited to entries from projects they belong to.

babelize tm list <projectId>                # List entries (owner: your whole TM)
babelize tm update <projectId> <entryId> --translation "nueva traducción"
babelize tm delete <projectId> <entryId>
babelize tm add <projectId> --source "Hello" --translation "Hola" --target-lang es
babelize tm export <projectId>              # Export your TM as TMX
babelize tm clear <projectId>               # Clear TM (with confirmation)

tm clear is owner-wide

babelize tm clear <projectId> deletes your entire translation memory — entries from every project you own, not just the named project. The CLI asks for confirmation before proceeding.

Projects

On this page