We’re the team behind Gatling, a load testing platform used by developers and SREs.
Today we’re releasing *Gatling Studio v1.0.3*, a native desktop app that turns a real browser session into a *ready-to-run Gatling load test*.
### *Why we built it*
Many teams struggle with the first mile of performance testing: capturing realistic user flows, cleaning out noise, and writing a complete scenario that reflects real behavior.
Existing recorders either capture too much noise, require plugins, or output code that needs heavy rewriting.
We wanted a way to go from:
*browser → clean scenario → runnable load test*
…with as little friction as possible.
### *How it works technically*
- Studio launches a controlled Chromium-based browser to capture all HTTP(S) traffic
- It stores the session as a HAR file in a local workspace
- It automatically groups sequential requests + generates pauses based on real user timing
- Static assets (images, fonts, analytics, etc.) can be filtered out
- You get a structured scenario with groups, exec blocks, pauses, and domain filtering
- Studio then exports a *complete Gatling project (Java/Maven)* you can run locally or move into Gatling Enterprise Edition for distributed load tests
### *What you can do with it*
- Record a web journey in one click
- Clean up the traffic to keep only meaningful requests
- Preview the exact scenario before generation
- Export runnable Gatling code
- Extend it, version it, automate it
- Push to GitHub or CI/CD immediately
stbrown80•1h ago
We’re the team behind Gatling, a load testing platform used by developers and SREs.
Today we’re releasing *Gatling Studio v1.0.3*, a native desktop app that turns a real browser session into a *ready-to-run Gatling load test*.
### *Why we built it*
Many teams struggle with the first mile of performance testing: capturing realistic user flows, cleaning out noise, and writing a complete scenario that reflects real behavior.
Existing recorders either capture too much noise, require plugins, or output code that needs heavy rewriting.
We wanted a way to go from:
*browser → clean scenario → runnable load test*
…with as little friction as possible.
### *How it works technically*
- Studio launches a controlled Chromium-based browser to capture all HTTP(S) traffic - It stores the session as a HAR file in a local workspace - It automatically groups sequential requests + generates pauses based on real user timing - Static assets (images, fonts, analytics, etc.) can be filtered out - You get a structured scenario with groups, exec blocks, pauses, and domain filtering - Studio then exports a *complete Gatling project (Java/Maven)* you can run locally or move into Gatling Enterprise Edition for distributed load tests
### *What you can do with it*
- Record a web journey in one click - Clean up the traffic to keep only meaningful requests - Preview the exact scenario before generation - Export runnable Gatling code - Extend it, version it, automate it - Push to GitHub or CI/CD immediately
### *Links*
- *Technical details & code samples* (GitHub): https://github.com/gatling/gatling-studio - *Product page*: https://gatling.io/product/studio - *Documentation*: https://docs.gatling.io/tutorials/low-code/browser/studio/
### *Notes*
Gatling Studio is a *proprietary tool* included in Gatling Enterprise Edition under the Enterprise Component License.
The core Gatling load testing engine remains open-source (Apache 2.0).