BrowserStack
BrowserStackExternal reviews
3,132 reviews
from
and
External reviews are not included in the AWS star rating for the product.
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.
Fast, Reliable Cross-Browser Testing on Real Devices—No Infrastructure Needed
What do you like best about the product?
BrowserStack helps me run fast, reliable cross-browser tests on a lot of real devices, without having to maintain any infrastructure myself.
What do you dislike about the product?
Since it runs in the cloud, you may also run into occasional performance slowdowns or latency issues.
What problems is the product solving and how is that benefiting you?
As a QA, I’m able to test the same software on multiple devices at once.
A handly tool for everyday testing needs.
What do you like best about the product?
1) Easy to test on multiple browser and real devices without any setup.
2) Saves a lot of time compared to maintaining physical devices.
3) Simple and clean interface, easy to use.
4) Quick switching between browser and devices.
5) Real device testing gives more accurate results than emulator.
2) Saves a lot of time compared to maintaining physical devices.
3) Simple and clean interface, easy to use.
4) Quick switching between browser and devices.
5) Real device testing gives more accurate results than emulator.
What do you dislike about the product?
Honestly, I don't have any major dislikes. Sometimes sessions can be a bit slow on busy devices. Apart from that, it works pretty smoothly for my needs.
What problems is the product solving and how is that benefiting you?
Browserstack solves a very practical problem for me - earlier, I had to either relly on emulator or manually test on limited devices, which often missed real world issues. Now I can quickly open my app on difference browser and real device in one place and actually see how it behaves.
This has helped me catch layout issues, responsiveness bugs and browser-specific problems much earlier. It saves me a lot of back and forth during QA and makes my releases more stable with less effort.
This has helped me catch layout issues, responsiveness bugs and browser-specific problems much earlier. It saves me a lot of back and forth during QA and makes my releases more stable with less effort.
BrowserStack Makes Quick, Easy Testing a Breeze
What do you like best about the product?
Browserstack is quite easy to use especially when I need to quickly run tests without a complicated setup process.
What do you dislike about the product?
I have noticed that the platform sometimes get slow or laggy which sometimes affect my testing experience.
What problems is the product solving and how is that benefiting you?
One of the problems Browserstack is currently solving is the problem of testing multiple apps across devices without even having the need to own them. This is beneficial to me because it allows me quickly test run my apps on real devices and detect issues on time.
Easy to Use with Flexible Configuration
What do you like best about the product?
It's easy to use and let me configure it
What do you dislike about the product?
It sends a lot of alerts and the ui could be improved
What problems is the product solving and how is that benefiting you?
Automate tests and send statistics
Flexible Device & Platform Selection for QA
What do you like best about the product?
Possibility to select different devices and platform to QA
What do you dislike about the product?
The UI a bit confusing some time. Especially selecting the different platform
What problems is the product solving and how is that benefiting you?
Showing other people how the app looks like without complicated setup or having a device
UI That Makes Mobile, Tablet, and Windows Testing Easy
What do you like best about the product?
The best thing is its simple user interface. It lets me do mobile, tablet, and Windows testing all on the same page, which makes everything easier to manage.
What do you dislike about the product?
The improvement I’d like to see is better compatibility for website iOS testing on iPhone.
What problems is the product solving and how is that benefiting you?
It helps me test my Angular website’s compatibility across different mobile devices and software platforms, such as iOS and Android.
Product is awesome, billing can be painful for enterprise customers
What do you like best about the product?
The tool is easy to use and there is a lot of mobile devices to select from and some of them are provided early, and that you have access to a lot of extra tools like screen recording with the base plans. We also like the fact that we can install apps from different sources.
What do you dislike about the product?
Billing is very frustrating with BrowserStack. We have lost access almost yearly and needed to get in touch with an account manager because of the issues in creating a PO for us to expense. Added to that you can only change your user count annually if your on an annual plan and our count fluctuates, it would be nice if BrowserStack offered a more flexible plan.
On the technical side the Android logs are robust, but the iOS logs can be flaky and either take a while to launch after the app is running or don't launch at all. Tablets are only on a few manufacturers it would be nice to have more tablets.
On the technical side the Android logs are robust, but the iOS logs can be flaky and either take a while to launch after the app is running or don't launch at all. Tablets are only on a few manufacturers it would be nice to have more tablets.
What problems is the product solving and how is that benefiting you?
Before we went remote during covid testers and developers shared a pool of physical devices in the office, once we went remote this strategy didn't work any longer. We tried mailing out devices to employees but it became a pain to manage these devices and the IP. First we turned to emulators but we found odd inconsistencies with some critical bugs not reproducible on an emulator (Examples: Android Studio/X-CODE) with the same device but present in the same physical device. BrowserStack offers us a wide range of remote physical devices our team(s) can access and we don't have to manage, they are wiped when the session ends and the tool has a similar interface for both Android and iOS with a lot of built in features - we don't need to train users on X-CODE and Android Studio and all the problems that comes with environment setup when we simply want our QA to test. We also like the fact that we can hook this up to our test automation.
A Pleasure to Use: Great UI and Broad Real-Device Testing
What do you like best about the product?
Being able to test across a wide range of real iOS, Android, and Windows devices and browsers without needing any physical hardware, along with the great UI and accessibility, is what makes it such a pleasure to use.
What do you dislike about the product?
Performance can sometimes feel slow or a bit laggy.
What problems is the product solving and how is that benefiting you?
BrowserStack addresses the challenge of testing across multiple browsers, devices, and operating systems without having to own or maintain physical hardware. It lets us quickly verify how our applications behave across different screen sizes, browsers, and mobile devices, which is especially valuable for responsive and accessibility-related testing. For us, this speeds up both exploratory and regression testing, helps surface layout and compatibility issues earlier, and provides broader coverage than we could realistically achieve using only local devices. It’s particularly useful as a supporting QA tool for validating changes across common user environments before moving on to real devices or a more formal sign-off process.
showing 11 - 20