AI Tools Tool updated 1 hour ago

Proxy Account Format Converter

Paste or upload AI proxy account files and convert them to the import format of another relay or gateway tool. The converter auto-detects ChatGPT sessions, Codex auth.json, CPA, Sub2API, Cockpit, 9Router, AxonHub, Codex-Manager, Claude Code, Gemini CLI and Qwen Code files for OpenAI/Codex, Claude, Gemini, Antigravity, Qwen, iFlow, Kimi, xAI/Grok, Kiro and GitHub Copilot accounts. Everything runs locally in your browser, so your tokens never leave your device.

Always Free Easy to use Instant results Private and secure

Use Proxy Account Format Converter

Runs 100% in your browser. Account JSON is parsed and converted locally. Nothing is uploaded, logged or stored. Treat access and refresh tokens like passwords: never publish them or commit them to Git.
1Import account JSON

Paste one or more JSON documents, JSONL, arrays or nested exports, or add multiple .json / .txt files. Formats and providers are detected automatically.

Used only when a token file has no provider marker, e.g. a bare Google OAuth token.
2Choose target format
3Review and download
Parsed accounts
0
Ready for target
0
Warnings
0
Skipped items
0
# Provider Account Detected source Expires Target
Import account JSON to see results.
Warnings
  • None
Skipped items
  • None
Tool Link
Copied to clipboard.
Share
Facebook Twitter WhatsApp Pinterest LinkedIn Telegram Reddit Tumblr VK Line
Help Improve This Tool
Report Request Comments

Read Content

Learn how the tool works and when to use it.

How to Use This Tool

1. Import account JSON

Paste one or more JSON documents, JSON Lines, arrays or nested exports into the import box, or drop several .json / .txt files. The converter walks through every object and detects the source format and provider automatically. If a file only contains a bare token without a provider marker, choose the provider in Provider for undetected accounts.

2. Choose the target format

Pick the tool you want to import into. Each target card lists the providers it supports. Turn on Remove duplicate accounts to merge repeated accounts, keeping the most complete and freshest record, and Differentiate account priority to give accounts imported first a higher priority.

3. Review and download

Check the parsed accounts table, warnings and skipped items, then copy the JSON or download it. Targets that need one file per account (such as CPA or Codex auth.json) are downloaded as a .zip. Download all formats creates one .zip with a folder for every supported target.

Supported Formats and Providers

  • Sub2API: OpenAI, Claude (anthropic), Gemini, Antigravity, xAI/Grok, Kimi, Kiro. Exported as a sub2api-data envelope for Account Management → Import Data.
  • CPA (CLIProxyAPI): Codex, Claude, Gemini, Antigravity, Qwen, iFlow, Kimi, xAI, Kiro. One auth file per account for the auth-dir (default ~/.cli-proxy-api). Gemini, Qwen and iFlow files are only loaded by older CLIProxyAPI releases.
  • Cockpit Tools: Codex and Antigravity accounts.
  • 9Router: Codex bulk import, plus providerConnections entries for Claude, Gemini CLI, Antigravity, iFlow, Kimi, xAI, Kiro and GitHub Copilot.
  • Codex auth.json: OpenAI Codex CLI credentials (ChatGPT sign-in or API key).
  • AxonHub: Codex auth JSON, Claude Code and GitHub Copilot OAuth JSON, and Antigravity refresh_token|project_id credentials.
  • Codex-Manager: batch import JSON for OpenAI accounts.
  • Claude Code, Gemini CLI and Qwen Code: native local credential files.

Source files can also be ChatGPT session JSON from chatgpt.com/api/auth/session. Missing email, account ID, plan and expiry values are read from the JWT access and ID tokens when available.

Features

  • Automatic format and provider detection across mixed inputs
  • JSON, JSONL, arrays, nested exports and multiple file uploads
  • Duplicate merging and optional priority ordering
  • Expired token and missing refresh token warnings
  • Per-account files packed into a .zip automatically
  • No server upload, no logging, no browser storage

FAQ

Short answers for the questions users ask before trusting the result.

No. Parsing and conversion run entirely in your browser with JavaScript. Nothing is uploaded, logged or saved. Access and refresh tokens are account credentials, so treat exported files like passwords and never publish or commit them.

An account is skipped when the target tool does not support its provider, when no access token, refresh token or API key is present, or when the provider cannot be detected. Choose a provider for undetected accounts or select a different target.

CLIProxyAPI reads one auth JSON file per account from its auth directory. The converter creates one file per account and packs them into a .zip when there is more than one.

No. Codex auth.json and Codex-Manager only accept OpenAI accounts. Claude, Gemini and Antigravity accounts can be exported to Sub2API, CPA, 9Router and the other targets that list them.

They are still converted, and a warning is shown. The target tool can refresh them if a refresh token is included.

Comments (0)

For user discussion, edge cases, and follow-up tips.
Leave a comment
Your comment will appear publicly after submission.
No comments yet. Be the first to comment!
Let Us Know!
Report an issue with this tool

Describe the issue you encountered so we can investigate and improve the tool.

What helps most
Include the input, expected result, actual result, browser/device, and a screenshot when helpful.
The screenshot button captures the page in the browser and attaches the generated image to this form.
Full-page screenshot
Captured in your browser with newisty.
No screenshot captured yet.
Tool Report