Use this file to discover all available pages before exploring further.
Gatling supports two distinct SDK families: the JVM SDK for Java, Kotlin, and Scala, and the JavaScript SDK for JavaScript and TypeScript. Both families expose the same load testing engine and produce identical HTML reports, so your choice of language is purely about ecosystem fit. This guide covers the installation process for every supported path: Maven, Gradle, sbt, and the JavaScript CLI. It also covers IDE setup and the standalone bundle for offline environments.
64-bit OpenJDK LTS, versions 11 through 25. Java 17 or 21 is recommended. The Azul JDK is a reliable choice.
Maven 3.6.3 or later — or use the Maven Wrapper bundled with the demo project (no system-wide Maven needed).
Git (optional, for cloning).
Verify your environment before continuing:
java -versionmvn -version
Gatling launch scripts and the Maven plugin respect the JAVA_HOME environment variable. If JAVA_HOME points at the wrong runtime you may see Unsupported major.minor version errors. Confirm the value before running tests.
Confirm that everything is wired up correctly by executing the demo simulation:
./mvnw gatling:test
The plugin will prompt you to select a simulation if more than one is present, or run the only available one automatically. The HTML report is written to target/gatling/.To run a specific simulation without the interactive prompt:
Same JVM prerequisites as Java: 64-bit OpenJDK LTS 11–25. Kotlin is compiled on the JVM — no separate Kotlin runtime installation is needed when using Maven or Gradle.
sbt 1.x installed, or use the Maven/Gradle starter projects instead.
Scala simulations compiled with long method chains may trigger a StackOverflowError in the Scala compiler. Increase the compiler stack size by setting -Xss100M in your IDE’s Scala compiler settings or in the sbt configuration.
The standalone bundle is intended for environments without internet access (for example, behind a corporate firewall). For all other situations, the Maven plugin is recommended — it is lighter and easier to commit to a Git repository.
The standalone bundle supports Java only — not Kotlin or Scala. For those languages, use a Maven, Gradle, or sbt project.
The bundle is based on a Maven Wrapper. Extract it, then open the project in an IDE such as IntelliJ IDEA.Bundle directory structure:
Path
Purpose
src/test/java
Your simulation source files (respect package hierarchy)
src/test/resources
Feeder files, request body templates, Gatling/Logback config
pom.xml
Maven project descriptor
target/
Generated test results
Windows users: do not place the bundle in the Programs folder (permission issues). Use 7-zip to extract the archive — the built-in Windows zip tool will not work correctly.
IntelliJ IDEA Community Edition supports Java, Kotlin, Maven, and Gradle out of the box. Open the project folder and IntelliJ will detect the build tool automatically.For Scala with sbt, install the Scala plugin from the JetBrains Marketplace. After installing it, increase the Scala compiler stack size to avoid StackOverflowError during compilation:
Go to Settings → Build, Execution, Deployment → Compiler → Scala Compiler.
Add -Xss100M to the compiler options.
VS Code works well for all Gatling SDK languages. Install the following extensions for the best experience:JVM languages: