BrowserStack Reviews & Product Details

I appreciate the ability to test on multiple mobile devices at once and see errors in detail through the test suite view. It's really handy to have three different devices open at once on different operating systems to test new features that might break on one screen size or an older OS that we still need to support. Review collected by and hosted on G2.com.

The UI is a bit clunky and moving around to find the page you need is pretty hard. I have to bookmark pages to make sure I can find my way around. There are menus within menus within menus on the sidebar. Also, the website is NOT mobile friendly. The docs are sorely lacking. Review collected by and hosted on G2.com.

It supports multiple devices and now includes a parallel feature, allowing me to test scenarios on different devices with various operating systems simultaneously. There is also support for local BrowserStack. I also appreciate the App Live and Live Platform features, which make the Appium setup more efficient, enabling easier automation of mobile applications. Review collected by and hosted on G2.com.

Sometimes the device is not available, and the latest updated version is not up to date. For example, while most physical devices now have Android 16, BrowserStack still only shows the older version, Android 15. Review collected by and hosted on G2.com.

Browserstack products are really answering actual QA needs. I have used and encourage the use of it across multiple teams and projects. The main feature that I think is the most valuable is the ability to test across multiple real devices and OS in real time. I don't need a physical device, that will probably become obsolete in just a few months, anymore. Review collected by and hosted on G2.com.

I guess the pricing is starting to become the main obstacle. Most team budgets could struggle to afford the different plans. And sometimes the performance while testing is not great as we often have lags. Review collected by and hosted on G2.com.

Browserstack has been extremely valuable for validating web applications across browsers, devices, and operating system without the overhead of maintaining a physical device. It fits naturally into modern development workflows, especially when working with CI/CD pipelines and automated test suites.

The real-device cloud is a major advantage-being able to instantly test on actual iOS and Android devices helps catch real-world issues that emulators often miss, such as touch behavior, rendering differences, and performance incosistencies.

I also appreciate how smoothly it integrates with automation frameworks and supports parallel execution, which significantly reduces testing time. The UI is clean, sessions are easy to manage, and debugginh tools like logs, screenshots, and video recordings make issue tracing much more efficient. Overall, it helps maintain high quality release which keeping the process fast and reliable. Review collected by and hosted on G2.com.

What I dislike about BrowserStack is that sometimes it takes a little time to start or switch between devices. But this is okay because it is working with real devices.

Overall, it's a small issue and does not affect my work much. Review collected by and hosted on G2.com.

I find BrowserStack to be a great tool for debugging website experiences. Being able to use different devices from iPhones to tablets and desktops is really helpful for handling problems that can't be replicated on our machines. We often ask clients about their OS and browser stack to recreate issues, which BrowserStack accommodates effectively. It's incredibly easy to use straight out of the box, which is a key feature I like. The setup was really easy, allowing us to get going quickly. The virtual aspect of it is great compared to desktop versions we've tried before. Review collected by and hosted on G2.com.

nothing. Review collected by and hosted on G2.com.

Honestly, the biggest win is not having to manage any physical devices or browser setups. I can just log in and start testing on real devices and different browsers immediately.

In my day-to-day work, I often need to quickly verify features across multiple environments, and Browserstack makes that easy. Running tests in parallel saves a lot of time, and the Selenium integration fits nicely into our existing CI pipeline. Debugging is also easier with session recording and logs- especially when somethings breaks and you need to quickly figure out why.

It’s one of those tools that just removes a lot of friction from the workflow. Review collected by and hosted on G2.com.

Sometimes sessions can be a bit slow or laggy, especially during busy times. I have also seen session drop occasionally, which can be annoying if you are in the middle of testing.

Pricing can be a concern too. It’s worth it if you use it properly, but for smaller teams it might feel a bit expensive. Review collected by and hosted on G2.com.

I use BrowserStack for cross-browser and real-device testing, which is great for validating UI consistency and ensuring compatibility across various browsers and devices. I like the real-device testing capability and how quickly I can spin up different browser/device combinations. This is especially useful for reproducing edge-case bugs and validating UI behavior that is hard to simulate locally. I appreciate how BrowserStack eliminates the need for maintaining an internal device lab and simplifies cross-browser testing. It allows me to debug issues specific to certain browser versions or devices, validate responsive behavior, and run regression checks in hard-to-replicate environments. I also enjoy how BrowserStack integrates well into existing QA workflows. Features like session recording, developer tools access, and the ability to quickly debug issues in specific environments are especially useful during regression testing. These features bring production-like environments closer to my development workflow, reducing the time spent reproducing and diagnosing cross-environment issues. Review collected by and hosted on G2.com.

One area where BrowserStack could improve is session performance and stability. At times, sessions can feel laggy, and reconnecting or restarting can interrupt workflow. Debugging can also be slightly slower compared to local environments, so optimizations around latency and faster session initialization would help. Reducing session startup time and making device/browser initialization more consistent would help avoid interruptions in the testing flow. It would also be useful to have better session recovery—so if a session drops, you can reconnect without losing all context. From a debugging perspective, more detailed logs around session failures or slowdowns (e.g., network latency, device load) would make it easier to understand what’s going wrong. Additionally, optimizing input responsiveness (typing, scrolling, interactions) would make remote sessions feel closer to local testing. Overall, improving reliability, faster reconnections, and better observability into session performance would significantly enhance the developer experience. Review collected by and hosted on G2.com.

I use BrowserStack for cross-browser and cross-device testing. It provides a variety of devices and browsers to verify that our application is free from UI issues, which gives me confidence as a QA to pass tickets. I appreciate having access to all the latest devices and browsers for conducting UI testing. The initial setup was really easy, as it only required credentials to use. Review collected by and hosted on G2.com.

Sometimes it gets stuck when opening links, and most of the time it feels slow. When I try to view a web page across multiple devices, I don’t see an option to close a specific device so I can add another one. Also, I can’t drag left or right to navigate the way I expect. Review collected by and hosted on G2.com.

I find BrowserStack easy to use, especially since it runs on real devices and even shows the hardware info. I appreciate the ease of switching to any OS or browser, and the initial setup was straightforward with just setting up an account and going. It's also incredibly valuable for testing multiple devices to ensure websites meet QA needs. It's particularly handy for testing specific issues that users report, like with an iPhone 16 on Safari, without needing to have the actual device. Running in Citrix is a great experience. Review collected by and hosted on G2.com.

sometimes network connection is buggy over VPN, especially if QA is offshore Review collected by and hosted on G2.com.

What I like best about Browserstack is how practical and time-saving it is in real work. I can instantly test my application on different browsers like Chrome, Firefox, Safari, and Edge, and also on real mobile devices without installing anything. This is very useful when I need to quickly check if a feature is working properly across multiple environments.

In daily work, it helps me reproduce issues easily. For example, if a bug appears only on a specific browser or device, I can directly open that setup in Browserstack and debug it. I can also test responsiveness and UI behavior on different screen sizes, which is very helpful.

Another thing I like is that it supports both manual testing and automation. So I can run quick manual checks as well as automated tests in the same platform. This makes the overall testing process faster, more reliable, and well organized. Review collected by and hosted on G2.com.

What I dislike about Browserstack is that sometimes starting a session or switching between devices can take a little time. But this is understandable because it is working with real devices in the cloud.

In a practical sense, it's a small trade-off for the convenience it provides. Overall, it still helps me save much more time compared to setting up and managing devices manually. Review collected by and hosted on G2.com.