With Homebrew, JMeter’s configuration files are in $(brew --prefix jmeter)/libexec/bin. That folder holds jmeter.properties and user.properties. On an Apple Silicon Mac the full path is /opt/homebrew/opt/jmeter/libexec/bin, and on an Intel Mac it is /usr/local/opt/jmeter/libexec/bin. The usual <jmeter home>/bin from the JMeter documentation maps to that libexec/bin folder.
Key takeaways
- Homebrew keeps the whole JMeter distribution in a
libexecfolder inside its own prefix, so<jmeter home>becomes$(brew --prefix jmeter)/libexec. - The prefix is
/opt/homebrewon Apple Silicon and/usr/localon Intel. Do not hard-code it: runbrew --prefix jmeter. - Put your own settings in
user.properties. Homebrew installs each version in its own folder, so abrew upgradestarts you with a fresh copy of the files.
Where is JMeter installed with Homebrew?
Run this in Terminal:
brew --prefix jmeterIt prints the stable path of the installed formula, for example /opt/homebrew/opt/jmeter on Apple Silicon. That path is a symlink to the versioned folder in Homebrew’s Cellar (for example /opt/homebrew/Cellar/jmeter/5.6.3), so it keeps working after an upgrade, while the Cellar path changes with every version. The JMeter files sit in libexec inside it:
ls "$(brew --prefix jmeter)/libexec"You will see the same layout as the archive from jmeter.apache.org: bin, lib, docs, extras and so on. The jmeter command on your PATH (/opt/homebrew/bin/jmeter on Apple Silicon) is a small wrapper script that sets JAVA_HOME and calls libexec/bin/jmeter.
Where are the JMeter configuration files with Homebrew?
| Item | Standard JMeter | Homebrew JMeter |
|---|---|---|
| JMeter home | <jmeter home> | $(brew --prefix jmeter)/libexec |
| Config and start scripts | <jmeter home>/bin | $(brew --prefix jmeter)/libexec/bin |
jmeter.properties | <jmeter home>/bin/jmeter.properties | $(brew --prefix jmeter)/libexec/bin/jmeter.properties |
user.properties | <jmeter home>/bin/user.properties | $(brew --prefix jmeter)/libexec/bin/user.properties |
| Dependency jars (libraries) | <jmeter home>/lib | $(brew --prefix jmeter)/libexec/lib |
| Plugins | <jmeter home>/lib/ext | $(brew --prefix jmeter)/libexec/lib/ext |
Open the folder in Finder or edit a file straight from Terminal:
open "$(brew --prefix jmeter)/libexec/bin"
nano "$(brew --prefix jmeter)/libexec/bin/user.properties"With these paths you can:
- change settings in
user.propertiesorjmeter.properties; - add a library jar that a plugin or a script needs to
libexec/lib; - add a plugin jar to
libexec/lib/ext. The Homebrew formula already puts the JMeter Plugins Manager jar there (see how to install plugins with the Plugins Manager).
Should I edit jmeter.properties or user.properties?
Edit user.properties. The JMeter manual says that to change the properties JMeter runs with you either modify user.properties in the bin directory or create your own copy of jmeter.properties and pass it on the command line (jmeter.apache.org/usermanual/get-started.html, read October 2026). Any property you set in user.properties overrides the default, and jmeter.properties stays as shipped, which makes it easy to see what you changed.
You can also keep your settings outside the install folder and load them with the -q option, which adds a property file to the run:
jmeter -n -t test.jmx -l results.jtl -q ~/jmeter/my-overrides.propertiesWill a brew upgrade overwrite my changes?
Assume yes. Homebrew installs every JMeter version into its own Cellar folder, and brew upgrade jmeter creates a new one. Files you edited, and plugin jars you copied into the old libexec, stay in the old version’s folder and are not in the new one. Copy user.properties and your plugin jars across after an upgrade, or keep your overrides in a separate file and load it with -q as above. The Plugins Manager can reinstall plugins from the new version’s UI.
Which Java does Homebrew’s JMeter use?
The current formula (JMeter 5.6.3, formulae.brew.sh, October 2026) depends on openjdk@21, and the wrapper script points JAVA_HOME at it. You do not need to install Java yourself. JMeter itself runs on Java 8 or newer (jmeter.apache.org/usermanual/get-started.html). Check what you have with brew info jmeter, and set JVM options such as heap size with the JVM_ARGS environment variable, for example JVM_ARGS="-Xms1g -Xmx4g" jmeter.
Installing from scratch? Follow how to install JMeter on Mac. Tired of typing the full path? Create an alias to start JMeter. When your test is ready, LoadFocus runs an existing .jmx file in the cloud from 25 regions, so you do not have to scale the test on your laptop.
Frequently Asked Questions
Why can I not find jmeter.properties after installing JMeter with Homebrew?
Homebrew does not create a normal apache-jmeter-x.y folder. It puts the distribution in a libexec folder inside its prefix, so the file is at $(brew --prefix jmeter)/libexec/bin/jmeter.properties.
What is the Homebrew prefix on Apple Silicon and Intel Macs?
It is /opt/homebrew on Apple Silicon and /usr/local on Intel Macs. Run brew --prefix to print yours, or brew --prefix jmeter for the JMeter folder.
How do I open the JMeter folder from Terminal?
Run open "$(brew --prefix jmeter)/libexec/bin" to show it in Finder, or cd "$(brew --prefix jmeter)/libexec/bin" to work in it.
Will my edits survive an upgrade?
Not automatically. A new version gets a new folder, so copy your user.properties and plugin jars across, or keep your overrides in a separate file and load it with -q.
