To record a mobile application with Apache JMeter, run JMeter’s HTTP(S) Test Script Recorder as a proxy, route the test device’s app traffic through the recorder, and trust JMeter’s generated certificate for HTTPS. The result is a draft JMeter test plan—not a finished load test—so you must inspect, correlate, parameterize, and validate the captured requests before replaying them.
What JMeter can record from a mobile app
The HTTP(S) Test Script Recorder intercepts HTTP and HTTPS traffic that passes through it and adds captured samples to a JMeter test plan. Apache describes the same recorder for a browser or a native application, although its detailed walkthrough uses a browser: Apache JMeter User’s Manual: Getting Started.
This means JMeter records network requests, not taps, screen transitions, local database operations, Bluetooth exchanges, or every protocol an app might use. Apache explicitly warns: “Do not use JMeter as the proxy for any other request types – FTP, etc. – as JMeter cannot handle them” (Component Reference).
An app must actually send its traffic through the proxy. Apps that bypass device proxy settings, use unsupported protocols, or enforce certificate-pinning or other interception protections may produce an incomplete capture or no usable capture. The official documentation does not guarantee that every Android or iOS application can be recorded.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches#1 Best Overall
- Please note, this device does not support E-SIM; This 4G model is compatible with all GSM networks worldwide outside of the U.S. In the US, ONLY compatible with T-Mobile and their MVNO's (Metro and Standup). It will NOT work with other CDMA carriers, and it is also not compatible with their MVNO (Visible, Xfinity Mobile, US Mobile, Cricket Wireless, etc).
- Compatibility with certain third-party devices and accessibility accessories, including some hearing aids, may vary depending on manufacturer support, Bluetooth protocols, software compatibility, and regional firmware limitations. For additional hearing aid compatibility information, please refer to Samsung’s official support documentation.
- Camera: 50 MP, f/1.8, (wide), 1/2.76", 0.64µm, AF | 50 MP, f/1.8, (wide), 1/2.76", 0.64µm, AF | 2 MP, f/2.4, (macro). Battery: 5000 mAh, non-removable | A power adapter is NOT included.
What you need before starting
- A JMeter installation on a computer reachable from the test device.
- A physical or virtual mobile test client containing the application and a repeatable test account or environment.
- A network path that allows the device to reach the computer’s recorder address and listening port.
- A test plan containing a Thread Group and, preferably, a Recording Controller. Apache’s best-practices guidance identifies these as the expected destination structure (Best Practices).
- Permission to intercept the application’s traffic in the test environment. Do not install a recording CA certificate on devices used for unrelated personal or production activity.
Set up the JMeter recording plan
- Open JMeter and create or open the test plan that will receive the recording.
- Add a Thread Group and place a Recording Controller inside it. The controller keeps recorded samplers together so you can identify and edit the captured journey later.
- Add and configure the HTTP(S) Test Script Recorder.
- Start the recorder and note its listening address and port. The step-by-step guide uses port 8888 as a default example, while the component reference says the port is configurable; use the value shown in your JMeter configuration rather than assuming 8888 (HTTP(S) Test Script Recorder: Step-by-step; Component Reference).
- Confirm that the recorder is saving new samples under the intended Recording Controller, then leave it running while you configure and exercise the client.
Route the mobile client through the JMeter proxy
Configure the test device’s active Wi-Fi or network connection to use the JMeter computer as its HTTP proxy. Enter an address that the device can reach on the network—not an address that exists only inside the JMeter computer—and enter the recorder’s actual listening port.
Android and iOS expose these controls in different places, and labels and certificate behavior vary by OS release, device-management policy, and application. The retrieved Apache material establishes the proxy requirement but does not verify current platform-specific tap paths. Consult the documentation for the exact Android or iOS version being tested instead of treating a particular menu sequence as universal.
Keep the device and JMeter host on a network where firewall rules permit the connection. If the device cannot open the proxy address and port, JMeter will receive no samples regardless of the app’s behavior.
Rank #2
- YOUR CONTENT, SUPER SMOOTH: The ultra-clear 6.7" FHD+ Super AMOLED display of Galaxy A17 5G helps bring your content to life, whether you're scrolling through recipes or video chatting with loved ones.¹
- LIVE FAST. CHARGE FASTER: Focus more on the moment and less on your battery percentage with Galaxy A17 5G. Super Fast Charging powers up your battery so you can get back to life sooner.²
- MEMORIES MADE PICTURE PERFECT: Capture every angle in stunning clarity, from wide family photos to close-ups of friends, with the triple-lens camera on Galaxy A17 5G.
- NEED MORE STORAGE? WE HAVE YOU COVERED: With an improved 2TB of expandable storage, Galaxy A17 5G makes it easy to keep cherished photos, videos and important files readily accessible whenever you need them.³
- BUILT TO LAST: With an improved IP54 rating, Galaxy A17 5G is even more durable than before.⁴ It’s built to resist splashes and dust and comes with a stronger yet slimmer Gorilla Glass Victus front and Glass Fiber Reinforced Polymer back.
Enable HTTPS recording safely
For HTTPS, JMeter generates a recording CA certificate. The client must trust that certificate so JMeter can terminate the client connection, inspect the request, and create a recording. Without that trust, the app or operating system will reject the interception connection. Apache describes an unknown_ca error as a likely sign that the client has not accepted the JMeter proxy certificate (Best Practices).
Free tools Windows power users keep installed
One-click scans. No signup required.
- Start the recorder and generate or locate its recording certificate as described in your JMeter version’s recorder documentation.
- Transfer it to the controlled test client using an approved method.
- Install and trust it only as required for this recording session and only on the test client. Some operating systems distinguish between certificates trusted for applications and those trusted only for network or user-installed credentials.
- After recording, remove the certificate and restore the device’s normal proxy and trust settings.
The properties reference documents a 7-day validity period as the default for generated recorder certificates; treat that as a JMeter configuration default, not a universal security or compatibility guarantee (Properties Reference).
Certificate trust does not defeat every app security control. An application that pins a server certificate or deliberately ignores the system proxy may still fail to connect or may expose only part of its traffic. Do not weaken production security controls to force a recording.
Rank #3
- Carrier: This phone is locked to Tracfone, which means this device can only be used on the Tracfone wireless network. Tracfone plan required, activating is easy, just 3 steps.
- DISPLAY: Immersive viewing on a 6.7-inch super-bright 120Hz display with powerful stereo speakers and Bass Boost for cinematic entertainment.
- CAMERA SYSTEM: Advanced 50MP Quad Pixel camera captures sharp, detailed photos and videos in any lighting condition
- PERFORMANCE: Lightning-fast 5G connectivity paired with a powerful processor and RAM Boost for smooth multitasking.
- BATTERY LIFE: Long-lasting 5000mAh battery with TurboPower charging technology delivers hours of power in minutes.
Capture a deliberate app journey
- With the proxy and, for HTTPS, certificate trust enabled, launch the app.
- Perform a small, known workflow such as sign-in, opening one account view, and completing one representative read or write action. Avoid generating unrelated background traffic while learning the flow.
- Stop recording after the journey. The recorder should have created HTTP request samplers under the Recording Controller.
- Inspect domains, methods, paths, status codes, headers, request bodies, and response data. Remove obvious noise such as analytics or update checks when those calls are outside the test objective.
- Compare the captured requests with the intended server-side transaction. A request appearing in the tree does not prove that the complete business operation was captured.
This start–exercise–stop–inspect workflow follows Apache’s browser recording example, adapted to a native client because the recorder operates as a network proxy (Step-by-step guide).
Turn the recording into a usable test
A recording is a request draft. The mobile client supplied state automatically during the live session; a JMeter replay must represent that state explicitly.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteHandle cookies and session state
Add or verify an HTTP Cookie Manager when the application uses cookies. Check that login cookies, session identifiers, and expiration behavior are represented correctly. Apache’s component guidance specifically calls out cookie handling when repairing recorded plans (Component Reference).
Rank #4
- YOUR CONTENT, SUPER SMOOTH: The ultra-clear 6.7" FHD+ Super AMOLED display of Galaxy A17 5G helps bring your content to life, whether you're scrolling through recipes or video chatting with loved ones.¹
- LIVE FAST. CHARGE FASTER: Focus more on the moment and less on your battery percentage with Galaxy A17 5G. Super Fast Charging powers up your battery so you can get back to life sooner.²
- MEMORIES MADE PICTURE PERFECT: Capture every angle in stunning clarity, from wide family photos to close-ups of friends, with the triple-lens camera on Galaxy A17 5G.
- NEED MORE STORAGE? WE HAVE YOU COVERED: With an improved 2TB of expandable storage, Galaxy A17 5G makes it easy to keep cherished photos, videos and important files readily accessible whenever you need them.³
- BUILT TO LAST: With an improved IP54 rating, Galaxy A17 5G is even more durable than before.⁴ It’s built to resist splashes and dust and comes with a stronger yet slimmer Gorilla Glass Victus front and Glass Fiber Reinforced Polymer back.
Correlate changing values
Find values that change between sessions or requests, such as CSRF tokens, access tokens, timestamps, and generated IDs. Extract the value from the relevant response and reference it in later requests rather than replaying the literal value captured on the device.
Parameterize test data
Replace one user, account, search term, or record ID with controlled variables or data files. Decide which data may be shared by virtual users and which must be unique to avoid collisions.
Repair authentication and headers
Inspect authorization headers, refresh-token exchanges, content types, device identifiers, and required custom headers. Remove headers that are device-specific or irrelevant to the server-side test, but retain those the API genuinely requires.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Best Value
- Charger NOT Included, 6.7" Super AMOLED FHD+, 90Hz Refresh Rate, 385 ppi, 800 nits (HBM), 1080x2340px, 5000mAh Battery
- 128GB, 4GB RAM, microSDXC, Exynos 1330 (5nm), Octa-Core, Mali-G68 MP2 or Mali-G57 MC2 GPU
- Rear Camera: 50MP, f/1.8 (wide) + 5MP, f/2.2 (ultrawide) + 2MP, f/2.4 (macro), LED flash, panorama, HDR; Front Camera: 13MP, f/2.0, Android 14, up to 6 major Android upgrades, One UI 6.1
- 3G: HSDPA 850/900/1700(AWS)/1900/2100; 4G LTE: 1/2/3/4/5/7/12/13/14/20/25/26/28/29/30/38/39/40/41/48/66/71, 5G: 2/5/25/41/66/71/77/78 SA/NSA/Sub6/mmWave - Nano-SIM + eSIM
- US Model – Global Connectivity – Compatible with Most GSM Carriers like T-Mobile, AT&T, MetroPCS, etc. Will Also work with CDMA Carriers Such as Verizon, Straight Talk.
Add checks and pacing
Add assertions that verify meaningful responses, not merely HTTP transport success. Insert timers or other pacing that reflects the intended user journey. A rapidly replayed recording can create an unrealistic workload even when every request succeeds.
Validate before loading
Run the repaired flow with one user against a non-production target, inspect server responses and JMeter results, and fix functional failures before increasing concurrency. JMeter is intended for load testing, but a captured app flow by itself does not establish realistic pacing, backend coverage, or valid performance conclusions (Apache JMeter project site).
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.HTTP and HTTPS recording compared
| Choice | What changes | Important limitation |
|---|---|---|
| HTTP | Route the client through the recorder; no JMeter CA trust step is required. | Only unencrypted HTTP requests that actually traverse the proxy are visible. |
| HTTPS | Route the client through the recorder and install/trust the generated recording CA for the controlled test. | Certificate-pinning, OS policy, or app-specific proxy behavior can prevent or limit capture. |
| Native-app client | Use the same proxy recorder with a device or emulator configured for it. | Apache’s detailed procedure is browser-focused; current Android/iOS menus and universal compatibility are not established. |
| Manual test-plan authoring | Write requests and test logic directly instead of using a capture draft. | Requires more initial effort but can avoid recorder noise and make correlation and workload design explicit. |
Troubleshoot common failures
No samples appear
- Verify that the device is using the JMeter computer’s reachable address, not an incorrect or loopback-only address.
- Verify the recorder is running and that the device uses its current port.
- Check firewall rules and confirm the device can reach the proxy host.
- Test whether the app honors the device proxy. If traffic bypasses it, JMeter cannot record that traffic.
- Stop JMeter temporarily and compare behavior. Apache notes that a client working only when JMeter is stopped may not be using the proxy as expected (Best Practices).
HTTPS reports unknown_ca or refuses to connect
- Confirm that the installed certificate is the one generated by the local JMeter recorder.
- Check that it is trusted in the scope used by the app and operating system.
- Check whether the app enforces certificate pinning or another anti-interception policy.
- Remove the certificate after the controlled test.
Localhost or local-target traffic is missing
Some clients bypass proxies for local addresses. Apache’s best-practices page suggests trying the machine hostname or a non-loopback IP instead of localhost (Best Practices). Mobile applications may apply additional routing rules, so confirm the behavior for the particular app and target.
The captured flow fails during replay
- Add or correct the Cookie Manager.
- Correlate dynamic tokens, IDs, and timestamps.
- Recheck authentication order and refresh-token handling.
- Compare request headers and bodies with a successful controlled client session.
- Confirm that the target environment still exposes the same endpoints and data.
The recording is incomplete
JMeter sees only traffic that traverses its proxy and falls within its supported HTTP(S) scope. Background services, alternate protocols, bypassed connections, and app security controls can all leave gaps. Treat the recording as evidence of observed requests, not proof that it represents every operation the app performs.
When to record and when to author manually
Use the recorder when you need a fast first-pass inventory of an app’s HTTP(S) conversation and can control the client’s network and trust settings. Author the plan manually—or substantially rewrite the recording—when the flow has complex authentication, extensive dynamic data, strict workload requirements, or traffic that cannot reliably traverse the proxy. In either case, the finished test must be validated against the intended server behavior before you draw performance conclusions.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
