Key takeaways
- Download the Plugins Manager jar (
jmeter-plugins-manager-2.0.jartoday) from jmeter-plugins.org/get, drop it into JMeter’slib/extfolder and restart JMeter. - After the restart, the manager is under Options > Plugins Manager, where the Available Plugins tab installs plugins and the Upgrades tab updates them.
- The manager installs a plugin together with the other plugins and libraries it depends on, which copying a single jar by hand does not.
To install the JMeter Plugins Manager, download its jar from jmeter-plugins.org/get, copy it into the lib/ext folder of your JMeter installation and restart JMeter. A new Plugins Manager entry then appears in the Options menu, and from there you install, update and remove plugins without touching the file system again.
What is the JMeter Plugins Manager?
The Plugins Manager is itself a small JMeter plugin. It reads the plugin catalog published on jmeter-plugins.org and lets you tick the plugins you want. It downloads each one together with the libraries it depends on and puts them into the right folders. Before it existed, you downloaded every jar by hand, hoped you had the dependencies right, and found out about a mismatch when JMeter failed to start.
You need a working JMeter first. JMeter 5.6.3 is the current release on jmeter.apache.org and requires Java 8 or later. If you have not installed it yet, our guide to installing JMeter on a Mac covers the Homebrew route, which already includes the Plugins Manager.
How do you install the JMeter Plugins Manager?
-
Check whether you already have it. Open JMeter and look at the Options menu. If there is a Plugins Manager item, skip to the next section.
-
Download the jar from jmeter-plugins.org/get. The link redirects to Maven Central; the file is named
jmeter-plugins-manager-2.0.jarat the time of writing (October 2026). Older tutorials call itJMeterPlugins-Manager.jar. -
Copy the jar into the
lib/extfolder of your JMeter installation, for exampleapache-jmeter-5.6.3/lib/ext. With Homebrew the folder is$(brew --prefix jmeter)/libexec/lib/ext. -
Close JMeter if it is running, then start it again with
bin/jmeter.baton Windows orbin/jmeter.shon Linux and macOS. -
Open Options and confirm that Plugins Manager is there.
If the entry is missing, the jar is in the wrong folder or JMeter was not restarted. Open jmeter.log in the bin folder to see whether the jar was loaded.
How do you install a plugin with the Plugins Manager?
Open Options > Plugins Manager. The dialog has three tabs: Installed Plugins, Available Plugins and Upgrades.
- Go to Available Plugins and use the search box to find the plugin you want.
- Tick its checkbox. The bottom pane lists what will change, including dependencies that come along.
- Click Apply Changes and Restart JMeter. JMeter downloads the files, restarts and loads the new elements.
A good first plugin is Custom Thread Groups (plugin id jpgc-casutg). The jmeter-plugins.org catalog lists it as adding the Stepping, Ultimate, Concurrency, Arrivals and Free-Form Arrivals Thread Groups, which let you shape a ramp-up and a steady load more precisely than the standard Thread Group. After the restart, right-click the Test Plan and choose Add > Threads (Users) to see them. For a plan that must hold a target request rate, the Throughput Shaping Timer (jpgc-tst) is another common choice. How ramp-up works in general is covered in our JMeter ramp-up period guide.
To check the result, reopen the Plugins Manager and look at the Installed Plugins tab. Everything you ticked should be listed there.
Which JMeter plugins are worth installing?
A handful of JMeter plugins cover most everyday needs. Search for each one by name or id on the Available Plugins tab (names and ids from the jmeter-plugins.org catalog, checked in November 2026). The first five rows cover most test plans; the last four help with scripting and debugging:
| Plugin | Id | What it adds |
|---|---|---|
| Custom Thread Groups | jpgc-casutg | Stepping, Ultimate, Concurrency, Arrivals and Free-Form Arrivals Thread Groups |
| Throughput Shaping Timer | jpgc-tst | A schedule of target requests per second |
| 3 Basic Graphs | jpgc-graphs-basic | Average Response Time, Active Threads and Successful/Failed Transactions graphs |
| 5 Additional Graphs | jpgc-graphs-additional | Response Codes, Bytes Throughput, Connect Times, Latency and Hits/s graphs |
| PerfMon (Servers Performance Monitoring) | jpgc-perfmon | Server resource metrics such as CPU and memory, collected by a ServerAgent you start on the target machine |
| Dummy Sampler | jpgc-dummy | A sampler that returns the result you define, for debugging a script without calling a server |
| Parallel Controller & Sampler | bzm-parallel | Runs its child elements in parallel to each other |
| Random CSV Data Set | bzm-random-csv | Reads a CSV file in random order |
| Custom JMeter Functions | jpgc-functions | Extra functions for common scripting needs |
Skip the old JSON/YAML Plugins: the catalog marks them deprecated, because core JMeter 4.0 and later does the same job.
How do you update or remove JMeter plugins?
When the catalog has newer versions of something you use, the menu entry reads Plugins Manager (has upgrades). Open the Upgrades tab, tick the plugins and apply the changes. To remove a plugin, untick it on the Installed Plugins tab and apply. Review the change list before you confirm: removing a plugin can also remove others that depend on it.
How do you install JMeter plugins from the command line?
The manager also has a command-line tool for servers and CI jobs where nobody opens the GUI. It needs cmdrunner-2.0.jar in lib and PluginsManagerCMD.sh (.bat on Windows) in bin. The jmeter-plugins.org page on command-line use explains where to get them if they are missing. The commands are:
PluginsManagerCMD.sh status
PluginsManagerCMD.sh available
PluginsManagerCMD.sh install jpgc-casutg,jpgc-tst
PluginsManagerCMD.sh install-for-jmx /path/to/testPlan.jmx
PluginsManagerCMD.sh uninstall jpgc-tst
install-for-jmx reads a test plan and installs the plugins that plan uses, which suits a pipeline that has to run someone else’s .jmx file. Restart JMeter afterwards so it loads the new jars. Behind a proxy, pass the proxy settings through the JVM_ARGS environment variable.
Why is the Plugins Manager not working?
- No Plugins Manager in the Options menu. The jar is not in
lib/ext, or JMeter was not restarted. Check the folder for the installation you actually launch, since a machine often has more than one JMeter. - The dialog is empty or the plugin list does not load. The manager downloads its catalog from jmeter-plugins.org, so it needs internet access. According to the jmeter-plugins.org documentation, an empty dialog can mean you are behind a proxy that needs configuring.
- The plugin list looks outdated. The same documentation says to delete the
pmgr_cachefolder under your Java temp directory (java.io.tmpdir) and reopen the dialog. - The installation fails with a permission error. The manager writes into JMeter’s
libfolders, so the user running JMeter needs write access there. This is most likely when JMeter sits in a system folder owned by an administrator. - A test plan opens with missing elements. The plan uses a plugin you have not installed. Install it from the Available Plugins tab, or run
install-for-jmxon the file.
Running plugin-based tests in the cloud
A plugin you installed on your laptop is not automatically on any other machine, and running your own distributed JMeter means keeping JMeter and its plugins identical on every load generator. With LoadFocus you upload the .jmx file and run it from the cloud locations; the product page says thread groups, CSV data, JSR223 samplers and plugins are preserved. Run a short test first to confirm your particular plugin behaves as it does locally.
Frequently Asked Questions
How do I get the Plugins Manager in JMeter?
Download the jar from jmeter-plugins.org/get, copy it into JMeter’s lib/ext folder and restart JMeter. The manager then shows up as Plugins Manager in the Options menu. If you installed JMeter with Homebrew, it is already there.
What are plugins in JMeter?
They are extra components that add elements JMeter does not ship with, such as thread groups, timers, listeners, samplers and graphs. Most are published through the jmeter-plugins.org catalog, which is what the Plugins Manager reads.
Do I need to restart JMeter after installing a plugin?
Yes. The Apply Changes and Restart JMeter button does it for you in the GUI. After a command-line install, restart JMeter yourself so it picks up the new jars.
Where do I run a JMeter script?
Open the .jmx file in the GUI to build and debug it. Run real tests in non-GUI mode, for example jmeter -n -t testplan.jmx -l results.jtl. Our guide to running JMeter in non-GUI mode has the full set of options.
How do I write my own JMeter plugin?
A plugin is Java code that extends one of JMeter’s component classes, compiled into a jar and placed in lib/ext. The jmeter-plugins.org site has a developer guide for this. For small bits of logic you often do not need a plugin at all; a JSR223 element with Groovy is enough.
Sources
- JMeter Plugins, Plugins Manager, jmeter-plugins.org/wiki/PluginsManager (October 2026)
- JMeter Plugins, Plugins Manager command-line tool, jmeter-plugins.org/wiki/PluginsManagerAutomated (October 2026)
- Plugins Manager source (tab names and button label), github.com/undera/jmeter-plugins-manager (October 2026)
- JMeter Plugins, developer guide, jmeter-plugins.org/wiki/DeveloperGuide (October 2026)
- JMeter Plugins catalog (plugin names, ids and descriptions), jmeter-plugins.org/repo (November 2026)
- LoadFocus JMeter load testing page, loadfocus.com/jmeter-load-testing (October 2026)
- Apache JMeter download page (5.6.3, Java 8+), jmeter.apache.org/download_jmeter.cgi (October 2026)