Tools

JMeter CLI Command Builder

Compose the exact jmeter and PluginsManagerCMD commands for your environment — no flag memorization required.

Ask about this page ChatGPT Claude Perplexity Gemini

Command type

Run test Install plugins Install + run

Operating system

macOS / Linux Windows

Test plan (.jmx) Results file (.jtl) Log file (optional) Remote servers (comma separated)

Generate HTML report (-e -o) Overwrite existing results (-f)

Report output folder Property overrides (one key=value per line, become -J flags)

Your command

Everything runs locally in your browser. The URL updates as you edit — share it to send the exact same configuration to a teammate.

Frequently asked questions

How do I run a JMeter test from the command line?

Use non-GUI mode: jmeter -n -t test-plan.jmx -l results.jtl. Add -e -o report-folder to generate an HTML dashboard report after the run, and -f to overwrite an existing results file. The GUI should only be used for creating and debugging test plans.

How do I install JMeter plugins from the command line?

Use the Plugins Manager command-line tool bundled with the Plugins Manager plugin: PluginsManagerCMD.sh install plugin-id-1,plugin-id-2 (or PluginsManagerCMD.bat on Windows). Plugin IDs are listed on each plugin page in the PerfAtlas directory.

How do I pass properties to a JMeter CLI run?

Use the -J flag for each property, for example -Jthreads=100 -JrampUp=60. Reference them inside the test plan with ${__P(threads,50)}. -J values only apply to the local run; use -G to propagate properties to remote servers in distributed testing.

How do I run JMeter in distributed mode from the CLI?

Add -R followed by a comma-separated list of remote server IPs or hostnames, for example jmeter -n -t plan.jmx -R 10.0.0.1,10.0.0.2. Each remote host must be running jmeter-server with the same JMeter and plugin versions.