Command Line Tool (Beta, Windows) — Reference & Batch Examples (Desktop)

Product: Deep Art Effects Desktop
Section: CLI & Automation
Scope: Windows‑only. The Command Line Tool is provided as a separate download (Beta).

Contents

• Purpose & scope
• CLI syntax (core command)
• Parameters
• Examples
  • Single image
  • PowerShell batch (folder)
  • Batch file (.bat) with style list
• Tips
• Troubleshooting
• See also

Purpose & scope

Use the Command Line Tool (Beta) to apply Deep Art Effects styles from the command line and to automate batch processing on Windows.

CLI syntax (core command)

<cli> artfilter -input <input_path> -output <output_path> -stylename "<Style Name>"

Run <cli> -help for the help text in your installed build.

Parameters

• artfilter — run the image style operation.
• -input <path> — source image file (e.g., .jpg/.png).
• -output <path> — full output path incl. filename and extension.
• -stylename "<Style Name>" — exact style name as shown in the Desktop app.

Examples

Single image (CMD/PowerShell)

<cli> artfilter ^
  -input "C:\images\source.jpg" ^
  -output "C:\images\out\source_Abstract_1.jpg" ^
  -stylename "Abstract 1"

PowerShell — process all JPGs in a folder with 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
}

Batch (.bat) — one image through a list of styles

Create styles.txt with one style name per line, then run.bat:

@echo off
set SRC=C:\images\portrait.jpg
set OUT=C:\images\out
for /f "usebackq delims=" %%S in ("styles.txt") do (
  <cli> artfilter -input "%SRC%" -output "%OUT%\portrait_%%S.jpg" -stylename "%%S"
)

Tips

• Use the exact style name (spacing/case) from the Desktop app.
• Quote paths with spaces ("C:\My Files\…").
• Start with a small test set before running large batches.
• Ensure the output folder exists and is writable.

Troubleshooting

• “Command not found” → Run from the CLI’s install folder or add that folder to your PATH.
• “Style not found” → Check the style spelling exactly as in the app/library.
• No output file → Verify the -output path/extension; ensure the destination folder exists and you have write permission.
• Immediate exit → Run from Command Prompt/PowerShell to read any messages and confirm you’re using the Windows CLI build.

See also

• Command Line Tool (Beta) — Install & Usage (Windows)
• Saving fails — how to fix (Desktop)
• File formats & quality (Desktop, FAQ)
• Optimize performance (Desktop)