BrowserStack Reviews & Product Details

I really like that BrowserStack provides instant access to real devices with various OS and browser versions, which makes cross-browser testing easy. We don't need to set up any virtual machines, saving us cost, time, and effort. It's fantastic that we can do both live and automation tests in the same place using BrowserStack. Access is instant through the cloud, and we can quickly replicate the desired OS and browser to test and share results. The BrowserStack dashboard is user-friendly and doesn't require any specific training. It ensures backward compatibility and helps validate UX consistency. Plus, BrowserStack doesn't require any hardware setup, and it works from any machine since it's cloud-based, so the initial setup didn't take more than 15 minutes. In the current market, BrowserStack outstands in performance and features, and I would recommend it on a scale of 10. Review collected by and hosted on G2.com.

BrowserStack has performance issues. Since we access the device/OS/browsers from the cloud, we find latency very often, and UI elements are not quickly clickable or accessible. Even logging into the application takes a delay most of the time. BrowserStack local tunneling is tricky for new users. A frequent issue faced was lag in screen updates after triggering actions. Also, sometimes button clicks and their response take delay. Form input sometimes registers keystrokes slowly. Automated test suites with more than 70+ test cases take more time to complete execution. Slower test execution due to extra network hops. Need a single command setup that handles firewall conflicts. Review collected by and hosted on G2.com.

The biggest advantage of BrowserStack is the wide range of real devices and browsers it offers. Being able to quickly test across different OS versions, browsers, and mobile devices without maintaining physical hardware is a huge productivity boost. The Live testing experience is smooth, device responsiveness is good, and session startup times are generally fast.

I also appreciate the integrations with popular tools like Selenium, Cypress, Playwright, and CI/CD pipelines, which makes it easy to plug BrowserStack into existing workflows. Debugging tools like console logs, screenshots, video recordings, and network logs are very helpful when investigating failures. Review collected by and hosted on G2.com.

Pricing can feel a bit high, especially for smaller teams or individual developers, and concurrency limits sometimes become a bottleneck when multiple people are testing at the same time. Occasionally, certain devices may feel slightly slower or unavailable during peak hours. The UI, while functional, could be more intuitive in a few areas, particularly when managing sessions or switching between devices. Review collected by and hosted on G2.com.

"The device coverage is a massive relief; having access to real hardware—from legacy Androids to the latest iPhones—without maintaining a physical lab is invaluable, though waiting in queues for popular devices can occasionally be frustrating. The logs are excellent, allowing us to view network requests and console errors on a remote device as if it were plugged into our own machines. Most importantly, the automatic video recordings are a game-changer for our workflow. Being able to attach video proof of a glitch directly to a ticket completely eliminates the 'I can't reproduce this' argument and speeds up fixes significantly." Review collected by and hosted on G2.com.

The input lag is the biggest frustration; because it’s streaming video, it’s often hard to distinguish between actual UI performance issues and just network latency.

The pricing is steep for what it is, making it a hard sell for smaller teams or individual developers.

Queues for popular devices (like the latest iPhone) are real; paying for a service and then waiting 5 minutes to get a phone feels wrong. Review collected by and hosted on G2.com.

What Works Really Well:

1. The idle warning system is brilliant - Before my session times out, I get a clear warning with a countdown timer. That ticking clock sound effect genuinely creates urgency and has saved me from losing sessions multiple times. It's both functional and effective!

2. Extensive real device coverage - The range of actual devices available is impressive. Being able to test on real hardware rather than just emulators catches issues that simulators miss, especially around touch gestures, performance, and device-specific bugs.

3. App installation flexibility - Multiple options to install apps (via Play Store, upload APK, or URL) makes testing different build versions straightforward and accommodates various workflow needs.

4. Session recording and debugging tools - The built-in video recording are essential for bug documentation. I can capture exactly what happened during a defect scenario. Review collected by and hosted on G2.com.

The Challenging Parts:

1. Google Play Store login flow has a recurring glitch - When testing apps that require Google sign-in through the Play Store, the session often resets during authentication. I'll be in the middle of logging in, and suddenly I'm back at an empty email field, forcing me to re-enter my credentials. This disrupts my testing flow significantly.

2. 10-minute idle timeout feels too restrictive - The maximum idle limit kicks in after just 10 minutes. As a QA professional reviewing test cases, taking screenshots, or documenting bugs, I often need more buffer time. I'm not sure if this varies by plan, but a 15-20 minute window would be more practical.

3. Unexpected session terminations - Sessions occasionally disconnect without warning, possibly due to internet connectivity issues on either end. When this happens, I lose my testing progress and have to restart the entire setup.

4. Limited concurrent sessions - I can't run multiple App Live sessions across different browsers simultaneously, which would really speed up my cross-device testing. Not sure if higher-tier plans offer this, but it would be a game-changer.

5. Initial device loading time - Some devices take 2-3 minutes to initialize, which adds up when you're testing across multiple configurations in a day. Review collected by and hosted on G2.com.

1. The ability to jump into any device or browser in seconds is honestly the biggest advantage. I don’t wait for emulators to boot or hunt for physical devices.

2. Touch response and scroll behaviour feel close enough to a real phone to reliably catch UI alignment, gesture issues, and responsive bugs.

3. Built-in tools like network throttling, geolocation, and device rotation make it easier to recreate real-world scenarios without using third-party utilities.

4. Screenshots and video recordings save time when creating bug reports, I can attach evidence instantly.

5. The consistency matters most. Whether it’s Chrome on a Pixel or Safari on an iPhone, I know exactly what environment I’m testing in. Review collected by and hosted on G2.com.

1. The visual frame rate occasionally drops for animation-heavy flows, making certain UI issues slightly harder to observe.

2. Switching between device orientations isn’t always instant, there’s a small lag. Review collected by and hosted on G2.com.

What I like best about BrowserStack is the ability to reliably test automation across a wide range of real browsers and real mobile devices without the overhead of maintaining local infrastructure. It allows me to quickly validate web and mobile applications in parallel across environments, which significantly speeds up feedback loops. The seamless integration with automation frameworks, stable cloud infrastructure, and accurate reproduction of real-world user conditions make it especially valuable for building and maintaining scalable test automation suites. Review collected by and hosted on G2.com.

What I dislike about BrowserStack is that test execution can occasionally be slower or inconsistent, especially during peak usage times, which can impact automation stability. Debugging failed tests can also be challenging at times due to limited visibility into device-level logs or transient environment issues. Additionally, managing sessions and optimizing parallel usage sometimes requires extra tuning to keep costs and execution time under control. Review collected by and hosted on G2.com.

I love using BrowserStack for its awesome feature of eliminating clutter by handling multiple devices for testing. The platform's ability to support Accessibility Testing is great, and I find the Low code automation to be a brilliant feature. The multidevice testing with sync is just mind-blowing as it lets me perform tests across multiple devices with the effort of testing just one. The guide line for setup is awesome, and it makes the initial setup super easy. I especially appreciate the BrowserStack support team—they're just one email away with mostly instant resolution SLAs. The Percy tool is also a favorite feature of mine. Review collected by and hosted on G2.com.

I find the sessions have a low idle timeout, and if that can be increased, it would be great. Also, nowadays all smartwatches support apps, so adding that section for live testing would be a great add-on feature. Review collected by and hosted on G2.com.

Parallel execution actually works reliably. When we run our full suite across multiple OS-browser combinations, the time savings are huge. The integration with popular frameworks (Selenium, Appium, Playwright, Cypress) is straightforward, you don’t waste time wrestling with configs. The session dashboard is clean: logs, video, network timelines, console output - all in one place. Debugging flakiness becomes much easier. Being able to run tests on real mobile + desktop devices without maintaining hardware is a massive operational relief. Build insights (pass/fail trends, flaky test detection, failure clustering) help identify problem tests faster. Review collected by and hosted on G2.com.

Occasional device allocation delays during peak hours can slow down CI pipelines. Video playback during debugging sometimes feels slightly laggy for animation-heavy flows. Network logs are useful but could be more detailed for deep investigation. If the suite has many retries, the dashboard can get cluttered without proper naming conventions. Review collected by and hosted on G2.com.

As a QA engineer, being able to test on real hardware instead of just some fake simulator is the best thing, because those simulators always lie, right? It just means when I find a bug, I know its a real bug the customer will actually hit. And the ability to fire up a test on some obscure old browser in like, two seconds? So smooth. It just makes the whole testing process way less painful. Review collected by and hosted on G2.com.

The main thing is that it can get real slow and laggy sometimes. You're trying to quickly check an animation on an old Android, but the mouse movements and screen updates are delayed, and it throws off the whole test. Review collected by and hosted on G2.com.

I like that BrowserStack provides instant access to a wide range of real devices and browsers, eliminating the need to maintain an internal device lab. The platform is extremely reliable, integrates well with existing CI/CD tools, and offers fast, accurate results. Its combination of live testing, automated testing, and debugging tools helps streamline the entire QA workflow. Review collected by and hosted on G2.com.

My main dislike is the latency when interacting with real devices, which can slow down debugging. Some features feel scattered, and advanced automation capabilities often require higher-tier plans. Device availability during high-traffic times can also be a challenge. Review collected by and hosted on G2.com.