BrowserStack
BrowserStackExternal reviews
3,132 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Exceptional Testing Capabilities, Needs More Accurate Emulation
What do you like best about the product?
I really enjoy using BrowserStack because it offers so many different variations of iPhone and Android formats, and all the different browsers. It's great to be able to check different version numbers and different tablets to ensure that responsiveness is working properly within a tool. We find it very helpful for team collaboration to make sure that everything is functioning properly. Initial setup was super easy, and I appreciate being able to log in and have access to check different versions and website browsers. It's very helpful to try out sandbox links on different devices to ensure our tool meets the responsiveness needed for most general models.
What do you dislike about the product?
Sometimes in BrowserStack, we don't see the same display that we do with actual physical devices. This discrepancy can lead to second guessing and double checking, making it really hard to tell what is the correct experience when troubleshooting an issue.
What problems is the product solving and how is that benefiting you?
BrowserStack helps us test our pharma coverage tool across different devices without owning them, which is great. It offers various iPhone and Android formats, browsers, and tablets, ensuring our tool's responsiveness works well, and aids team collaboration.
Easy Cross-Browser & Real-Device Testing with BrowserStack
What do you like best about the product?
Mainly about BrowserStack is how easy it makes cross-browser and real-device testing.
What do you dislike about the product?
Sometimes it's a little slow, which slows me down
What problems is the product solving and how is that benefiting you?
Testing across browsers and platforms, making catching compatibility issues much easier
User-Friendly Interface with Room for Android Improvements
What do you like best about the product?
I like the ease of use and the user-friendly interface of BrowserStack. It has extensive tools that make my work smoother. I appreciate the ability to use a particular device of choice and easily sideload apk/ipa files, as well as install apps directly from the App Store or Play Store. The initial setup was easy, thanks to the excellent onboarding sessions and walkthroughs provided.
What do you dislike about the product?
{"Load times, sometimes very busy.","Fragmentation support, in particular Android ones where not all OS versions are covered."}
What problems is the product solving and how is that benefiting you?
I use BrowserStack for cross-device and multi-device app testing, and accessibility testing.
Best tool for testing multiple locations, crossbrowsers and multiple scenarios.
What do you like best about the product?
Real Device Accuracy: Testing on actual iPhones/Pixels beats emulators for finding hardware-specific UI bugs.
Zero Maintenance: No need to manage a physical device lab or update OS/Browsers manually.
Instant Scaling: Running 50+ automation scripts in parallel turns a 2-hour test suite into 5 minutes.
Local Testing: The binary tunnel is the most reliable way to test "localhost" or staging environments securely.
Debug Artifacts: Automatic video recordings and network logs make "Steps to Reproduce" incredibly easy for developers.
Zero Maintenance: No need to manage a physical device lab or update OS/Browsers manually.
Instant Scaling: Running 50+ automation scripts in parallel turns a 2-hour test suite into 5 minutes.
Local Testing: The binary tunnel is the most reliable way to test "localhost" or staging environments securely.
Debug Artifacts: Automatic video recordings and network logs make "Steps to Reproduce" incredibly easy for developers.
What do you dislike about the product?
Latency/Lag: Remote sessions can be laggy, making "smooth" UI interactions feel choppy over a slow connection.
High Pricing: It is significantly more expensive than competitors like Sauce Labs or LambdaTest for small teams.
Slow Cold Starts: Booting up a specific real device or VM can sometimes take 30–60 seconds, which hurts productivity.
High Pricing: It is significantly more expensive than competitors like Sauce Labs or LambdaTest for small teams.
Slow Cold Starts: Booting up a specific real device or VM can sometimes take 30–60 seconds, which hurts productivity.
What problems is the product solving and how is that benefiting you?
Every problem related to testing.
Seamless Cross-Device Testing with Real Usability
What do you like best about the product?
I really like the usability of BrowserStack, it's very good. The fact that BrowserStack uses real devices is great! The initial setup was very easy since I used the web version and the VPN config, so I didn't need to do any real installation.
What do you dislike about the product?
Sometimes we have issues with applying a VPN profile when viewing devices/browsers.
What problems is the product solving and how is that benefiting you?
I use BrowserStack for testing features and bugs on different mobile devices and browsers. It helps identify issues that don't work across various devices and is really usable, thanks to the real devices feature.
Feature-Rich and Easy to Use
What do you like best about the product?
I really like the number of features it offers, and it’s easy to use.
What do you dislike about the product?
The UI could be improved by splitting and organising features more clearly
What problems is the product solving and how is that benefiting you?
Multi browser and device testing as we wouldn't be able to manually test each device
Feature-Rich Devices with Impressively Low Latency
What do you like best about the product?
Best devices with all features and low latency
What do you dislike about the product?
New Dashboard is confusing to use after a lot of usage from old dashboard
What problems is the product solving and how is that benefiting you?
For providing a lot of real devices to test on the cloud without having them on premises in low price.
A Lifesaver for App Testing Across Devices
What do you like best about the product?
I use BrowserStack for app automation and app testing. I appreciate that app automation allows me to have end-to-end testing, and the app live feature makes it possible to test on multiple devices. I like the number of devices and variety of operating systems available since I can't have physical devices due to cost. It lets me test my app on both lower-end and higher-end devices, and on various OEMs, which is great for testing in different environments. The initial setup of BrowserStack was easy and the process was simple.
What do you dislike about the product?
The UI could be improved. It lacks feedback to user input and it looks quite sluggish even on high-end devices like the MacBook Pro M5.
What problems is the product solving and how is that benefiting you?
I use BrowserStack for app automation and testing, allowing end-to-end testing and testing on multiple devices. It solves device cost issues by enabling testing on a variety of emulated devices and OS, including lower and higher-end devices and differing OEMs.
Frictionless Real-Device Testing at Scale—Fast Setup, Strong Automation, Broad Coverage
What do you like best about the product?
What stands out most about BrowserStack is how frictionless it makes real-world testing.
Instead of maintaining your own device lab (which is expensive, flaky, and constantly outdated), you get instant access to a huge matrix of real devices, browsers, and OS versions—all in the cloud. That alone removes a massive operational burden.
A few specific things that are especially strong:
Real device testing (not just emulators)
You’re testing on actual iPhones, Android devices, and desktop browsers, which catches issues emulators often miss—especially around performance, rendering, and touch behavior.
Zero setup / fast feedback loop
No installs, no VM wrangling. You can spin up a session in seconds, which is great for debugging production issues quickly.
Strong automation support
Works well with Selenium, Cypress, Playwright, etc., so you can plug it straight into CI/CD pipelines without reinventing your test infra.
Parallel testing at scale
You can run many tests simultaneously, which drastically cuts down CI time—super useful when your test suite grows.
Local testing tunnel
Their local tunnel feature makes it easy to test staging or localhost environments securely without exposing them publicly.
Reliable cross-browser coverage
It’s one of the easiest ways to ensure your app behaves consistently across Chrome, Safari, Edge, Firefox, and various OS combinations.
If I had to summarize it in one line:
👉 it replaces a complex, high-maintenance testing infrastructure with an on-demand, scalable service that “just works.”
If you’re evaluating it vs alternatives like Sauce Labs or LambdaTest, I can break down the trade-offs too.
Instead of maintaining your own device lab (which is expensive, flaky, and constantly outdated), you get instant access to a huge matrix of real devices, browsers, and OS versions—all in the cloud. That alone removes a massive operational burden.
A few specific things that are especially strong:
Real device testing (not just emulators)
You’re testing on actual iPhones, Android devices, and desktop browsers, which catches issues emulators often miss—especially around performance, rendering, and touch behavior.
Zero setup / fast feedback loop
No installs, no VM wrangling. You can spin up a session in seconds, which is great for debugging production issues quickly.
Strong automation support
Works well with Selenium, Cypress, Playwright, etc., so you can plug it straight into CI/CD pipelines without reinventing your test infra.
Parallel testing at scale
You can run many tests simultaneously, which drastically cuts down CI time—super useful when your test suite grows.
Local testing tunnel
Their local tunnel feature makes it easy to test staging or localhost environments securely without exposing them publicly.
Reliable cross-browser coverage
It’s one of the easiest ways to ensure your app behaves consistently across Chrome, Safari, Edge, Firefox, and various OS combinations.
If I had to summarize it in one line:
👉 it replaces a complex, high-maintenance testing infrastructure with an on-demand, scalable service that “just works.”
If you’re evaluating it vs alternatives like Sauce Labs or LambdaTest, I can break down the trade-offs too.
What do you dislike about the product?
Even though BrowserStack is solid overall, there are a few consistent pain points people run into:
1. Cost scales quickly
It’s fine for small teams, but once you start doing heavy parallel testing or need lots of device minutes, pricing ramps up fast. It can become one of the more expensive parts of your CI stack.
2. Session stability can be inconsistent
You’ll occasionally hit:
dropped sessions
devices getting stuck mid-test
random timeouts
Not constant, but enough to be annoying in CI pipelines where reliability matters.
3. Slower than local execution
Even with good infra, cloud devices introduce latency:
UI interactions feel slightly laggy
tests run slower than local/emulator setups
This becomes noticeable with large test suites.
4. Debugging can be painful
Logs, videos, and screenshots help, but:
reproducing flaky issues locally isn’t always straightforward
error messages can be vague
You sometimes end up re-running tests multiple times just to understand what failed.
5. Limited control over environment
Compared to running your own device farm:
you can’t fully control device state
OS/browser versions aren’t always the exact ones you want
background processes or network conditions are less configurable
1. Cost scales quickly
It’s fine for small teams, but once you start doing heavy parallel testing or need lots of device minutes, pricing ramps up fast. It can become one of the more expensive parts of your CI stack.
2. Session stability can be inconsistent
You’ll occasionally hit:
dropped sessions
devices getting stuck mid-test
random timeouts
Not constant, but enough to be annoying in CI pipelines where reliability matters.
3. Slower than local execution
Even with good infra, cloud devices introduce latency:
UI interactions feel slightly laggy
tests run slower than local/emulator setups
This becomes noticeable with large test suites.
4. Debugging can be painful
Logs, videos, and screenshots help, but:
reproducing flaky issues locally isn’t always straightforward
error messages can be vague
You sometimes end up re-running tests multiple times just to understand what failed.
5. Limited control over environment
Compared to running your own device farm:
you can’t fully control device state
OS/browser versions aren’t always the exact ones you want
background processes or network conditions are less configurable
What problems is the product solving and how is that benefiting you?
🔧 The core problems it solves
1. Fragmentation across browsers & devices
Users are on Chrome, Safari, Edge… iPhones, Androids, tablets, old OS versions, etc.
Testing all combinations manually is nearly impossible.
➡️ BrowserStack gives access to thousands of real browser/OS/device combos in one place
2. No need to maintain a device lab
Without it, you’d need to:
buy and manage physical devices
keep them updated
deal with breakage, OS upgrades, etc.
➡️ It eliminates the cost and maintenance overhead of in-house labs
3. Slow and manual testing workflows
Traditional QA:
repetitive manual checks
slow regression cycles
bottlenecks before release
➡️ BrowserStack enables automation + parallel testing, speeding up releases and feedback loops
4. Lack of realistic testing environments
Local setups often don’t reflect:
real device performance
real browser quirks
production-like conditions
➡️ It provides real devices and environments, not just simulations, improving accuracy
1. Fragmentation across browsers & devices
Users are on Chrome, Safari, Edge… iPhones, Androids, tablets, old OS versions, etc.
Testing all combinations manually is nearly impossible.
➡️ BrowserStack gives access to thousands of real browser/OS/device combos in one place
2. No need to maintain a device lab
Without it, you’d need to:
buy and manage physical devices
keep them updated
deal with breakage, OS upgrades, etc.
➡️ It eliminates the cost and maintenance overhead of in-house labs
3. Slow and manual testing workflows
Traditional QA:
repetitive manual checks
slow regression cycles
bottlenecks before release
➡️ BrowserStack enables automation + parallel testing, speeding up releases and feedback loops
4. Lack of realistic testing environments
Local setups often don’t reflect:
real device performance
real browser quirks
production-like conditions
➡️ It provides real devices and environments, not just simulations, improving accuracy
Comprehensive Device Testing Made Easy, But Can Lag
What do you like best about the product?
I use BrowserStack for testing surveys across different environments and devices, which is incredibly helpful in understanding how they will look on specific devices. I like that there's no need to purchase various devices, as BrowserStack’s virtual device simulators allow easy testing. The capability to replicate multiple device environments at once is great, letting us test simultaneously across Apple devices and Android. Running both types of operating systems at the same time lets us compare and optimize our software effectively. The initial setup was technical, but seamless.
What do you dislike about the product?
Sometimes it may get lagged and slowness can be observed when running more than 10 environments at once. While running multiple device environments users expect them to work as real devices without any latency.
What problems is the product solving and how is that benefiting you?
I use BrowserStack to test surveys on different devices, identifying errors in advance. It saves us from buying multiple devices, replicating environments for simultaneous testing on Apple and Android. This helps optimize our software effectively.
showing 11 - 20