Short answer
.\cli\JustConverter.Cli.exe is the command-line interface (CLI) included with Just Converter.
Open PowerShell in the app's installation folder, run one test file first and add --json when
another script needs a structured result it can read.
When to use this method
The CLI is useful for repeatable local jobs and scripts. It does not turn unsupported input into a valid conversion and it should not expose passwords or private contents in logs.
How we checked this guideSee what we reviewed, what we confirmed, and where the feature stops.
- What we reviewed
- Reviewed the command-line contract, supported arguments, JSON result format and exit codes, which tell a calling script whether the job succeeded.
- What we confirmed
- The command accepts input paths, format, output, profile, collision mode, recursion and JSON output through a documented contract.
- Important limit
- Shell success is not a fidelity check. A script must inspect the returned status and validate the created files.
What you need before using the command line
The command line is useful when another script needs a clear success or failure result instead of buttons. You still need a supported input, a writable output folder, and settings that pass the compatibility check.
Open the Just Converter installation folder in File Explorer. Click the address bar, type powershell, and press Enter. If PowerShell is already open elsewhere, use the executable's full path in quotation marks.
Start with a copy in a test folder. JSON is structured text that a script can read. An exit code is the small result number returned when the command ends.
Build a reliable command
Test one representative input
From the installation folder, try
.\cli\JustConverter.Cli.exe convert --input .\photo.png --format jpg --output .\converted.
Replace photo.png with a copied test file. Confirm the preflight check and open the result
before adding a folder.
Add recursion deliberately
Use recursive discovery only when nested folders are intended.
Choose collision behavior
Select rename, overwrite or skip explicitly instead of relying on an assumption.
Read JSON and exit codes
Read the structured JSON result and the documented exit code. Together they tell the calling script what happened; then verify the output files.
Checkpoint: trust the result only when three signals agree
Before adding recursion or a scheduler, run one representative file. The process exit code must indicate success, the JSON entry for that file must report success and the expected output must open correctly. If any one of those signals disagrees, stop and inspect the command and per-file result.
Documented command shape
Angle brackets below represent values supplied by the caller.
Scroll the table horizontally on a narrow screen.
| Part | Example |
|---|---|
| Command | .\cli\JustConverter.Cli.exe convert --input <path>... --format <format> |
| Optional output | --output <directory> --profile <id> |
| Collision and discovery | --collision rename|overwrite|skip --recursive |
| Machine-readable status | --json |
| Exit codes | 0 success; 1 usage or validation error; 2 no successful outputs; 3 partial success; 4 canceled; 5 required engine missing; 6 security or resource limit; 7 input/output or system failure |
If the command fails or returns mixed results
Read the JSON result for each file before looking only at the final exit code. Check quoted paths, the chosen operation, output permissions, collision behavior and optional components. Do not treat a created file as proof of success until the result status and the file itself both pass inspection.
Command-line automation mistakes
- Logging passwords or private file contents
- Using overwrite before checking the destination folder
- Ignoring nonzero exit codes or per-file status
Command checks
- One representative file succeeds first.
- The result reports every name conflict.
- JSON status and created outputs agree.
Just Converter
Convert supported images, media, documents, and PDFs on your PC. Check compatibility first, reuse saved settings, watch folders, or the command line, and retry only failed files.