Product: Deep Art Effects Desktop
Section: CLI & Automation
Note: The Command Line Tool (Beta) is a separate download from the desktop app.
Contents
- What the CLI is for
- Download & install (Windows)
- Verify the installation
- Basic usage
- Batch processing examples
- Update or uninstall
- Troubleshooting
- See also
What the CLI is for
- Render images without the GUI from your terminal or scripts.
- Apply a specific style by name and set supported options exposed by the CLI.
- Automate batch workflows on Windows.
Download & install (Windows)
- Open the official Downloads page and get Command Line Tool (Beta) for Windows.
- Run the installer and choose a folder (e.g.,
C:\DeepArtCLI). - (Optional) Add that folder to your PATH so you can call the CLI from any directory.
The CLI is code‑signed.
Verify the installation
Open Command Prompt or PowerShell and run the help command. You should see usage text and available commands/flags.
<cli> -help
If the shell can’t find the command, cd into the install folder or add it to your PATH.
Basic usage
Render a single image with a named style (Windows paths):
<cli> artfilter ^ -input "C:\path\to\source.jpg" ^ -output "C:\path\to\out\scene_Abstract_1.jpg" ^ -stylename "Abstract 1"
Use
-helpto list all flags supported by your installed CLI build.
Batch processing examples
Windows (PowerShell)
Process every .jpg in a folder using one style:
$IN = "C:\images\in"; $OUT = "C:\images\out"; $STYLE = "Abstract 1"
Get-ChildItem $IN -Filter *.jpg | ForEach-Object {
$dst = Join-Path $OUT ("{0}_{1}.jpg" -f $_.BaseName, $STYLE.Replace(' ','_'))
& <cli> artfilter -input $_.FullName -output $dst -stylename $STYLE
}Tip: Start with a small test set to confirm paths and the exact style name (as shown in the app/library).
Update or uninstall
- Update: Download the newer Command Line Tool (Beta) for Windows and run the installer (or replace the executable in your install folder).
- Uninstall: Use Settings → Apps → Installed apps to remove it, or delete the CLI folder if no uninstaller is present.
Troubleshooting
- “Command not found” → Add the CLI folder to your PATH or invoke it with the full path.
- “Style not found” → Use the exact style name from the Desktop app’s library.
- Immediate exit → Run from a terminal to read any error output; confirm you downloaded the correct OS build.
- Slow or stalled batch → Close other apps to free memory; try smaller batches first.
See also
- Command Line Tool (Beta, Windows) — Reference & Batch Examples (Desktop)
- Install on Windows (Desktop)
- Saving fails — how to fix (Desktop)
- File formats & quality (Desktop, FAQ)
- Optimize performance (Desktop)
Comments
0 comments
Please sign in to leave a comment.