BrowserStack Reviews & Product Details

What I like best about BrowserStack is how easy it makes cross‑browser and cross‑device testing. Having instant access to a wide range of real devices and browsers saves a huge amount of setup time and allows us to catch issues early that we’d otherwise miss locally. It integrates well with our existing automation setup and is reliable enough to be part of our CI pipeline. Review collected by and hosted on G2.com.

The main downside for me is that test execution can occasionally feel slow or queued during peak usage, especially when running larger automation suites. There can also be some instability with certain browser/device combinations, which sometimes requires re‑runs. Review collected by and hosted on G2.com.

I mainly use BrowserStack for cross-browser and real device testing during our QA cycles. It helps me quickly validate how our web applications behave across different browsers, OS versions, and mobile devices without maintaining a physical device lab. The testing capabilities all in one place really stand out to me. I've found their tools like Low Code Automation useful for quickly creating test flows without writing full automation scripts, and Percy for catching subtle UI shifts during visual regression checks. I also like features like local testing funnels, network throttling, and test analytics, which make debugging issues during CI runs much easier. These features save a lot of practical effort by letting me reproduce real user conditions and quickly see patterns behind failing tests instead of digging through raw logs. The initial setup for BrowserStack was fairly straightforward, and the documentation and sample configs helped speed things up for the team. Review collected by and hosted on G2.com.

One area where BrowserStack could improve is session stability - occasionally I have seen device sessions disconnect or slow down during longer manual testing runs. Another challenge is that test execution in the cloud can sometimes be slower compared to running locally, especially in large automation suites. I also feel the pricing can get expensive as teams scale usage across multiple parallel tests and projects. Review collected by and hosted on G2.com.

I love that BrowserStack provides a wide range of devices for testing mobile and web apps, which eliminates the need to own specific models like an iPhone or Samsung. It’s great that it feels like using an actual device rather than an emulator. I appreciate being able to explore the device itself, which lets me check out settings and features beyond just the app I am testing. BrowserStack is particularly valuable because it includes devices that are less common or no longer popular, which helps us handle customer complaints effectively. Joining the team on BrowserStack was a simple process, just requiring an email invite. Review collected by and hosted on G2.com.

I feel the debugging could be a bit better, if I can see console logs from the apps in the device would be really helpful. Also installing the apps takes a bit of time, but I don't think that is a BrowserStack issue. Review collected by and hosted on G2.com.

I use BrowserStack for testing the Clarity SDK JS version in real scenarios. I appreciate the wide range of real devices it offers, which helps detect issues before release. I like the rich variety of devices, operating systems, and the network monitoring features that help in pinpointing where issues actually occur. The initial setup was super easy, which was a big plus for my team. Review collected by and hosted on G2.com.

While using BrowserStack, I feel like it could be improved by adding some AI features. It would be really helpful if it could review the session and provide a detailed analysis of errors and logs. Having a tab for each session that shows what went wrong, with error details grouped by types of errors, and providing a report with that analysis would make things better. Review collected by and hosted on G2.com.

I mainly use BrowserStack for testing the responsiveness of my designs to see how they behave in the real world. It really saves me a lot of time compared to having multiple windows open with emulated or simulated device resolutions. I appreciate the cross-browser testing and the option to automate tests with the browser automation grid, which are probably my go-to features. The initial setup was really easy and 100% intuitive; we found no issues. Review collected by and hosted on G2.com.

I mean, maybe not just the feature. It's but, yeah, the pricing could be a little, like, more forgiving. That's one thing. But, also, I'm not, like, a huge fan of how the report end result slash form slash design of the report pages are, is broken. Think that's a little bit closet and too much information. That could be, like, much better, structure in terms of the information architecture and just the overall layout of it. Review collected by and hosted on G2.com.

I like that BrowserStack allows me to use local testing through the company network and offers a variety of different devices. This helps me a lot because staging servers are not accessible through real test devices or personal mobile phones, and using BrowserStack local testing is a much faster solution. Review collected by and hosted on G2.com.

The loading screen of the mobile devices sometimes takes a while. Setting up the local test environment on BrowserStack was a bit of a hassle. The user experience on mobile devices is sometimes a bit slow and laggy. The debug options on mobile devices could be improved; it's really difficult to inspect the code or get the correct container with the debug tools provided by BrowserStack. Review collected by and hosted on G2.com.

I find BrowserStack to be a great mobile testing tool, especially for testing on real devices in the cloud. It provides me with flexibility to test different platforms and versions of devices all under one roof. I really like how it supports both hybrid and native applications. It's pretty handy because it allows access to different platforms like web, iOS, and Android, and it lets me test on multiple devices simultaneously. Additionally, it's easy for any new user to get started with. Review collected by and hosted on G2.com.

Unable to test the color code confirmation of prototypes by inspecting element. Users should be able to verify the color codes for the elements by inspecting the element, just like in web. Review collected by and hosted on G2.com.

I use BrowserStack for mobile and web testing, and it's great for testing our apps on different browsers, OS, and proxy locations. I appreciate the App Live feature because it allows me to conveniently launch any OS and browser at any time and specify the OS version. It's extremely simple to set up, and our admins can easily manage users and their access. The ability to test on various resolution devices and across the latest simulators and OS variants reduces our testing time significantly. I'd definitely recommend BrowserStack to a friend or colleague, giving it a 10 out of 10. Review collected by and hosted on G2.com.

Sometimes, sessions are disconnected when launching multiple tabs and launching it quickly by changing devices. I would like more user-friendly messages on why there is a session exit suddenly. Review collected by and hosted on G2.com.

I use BrowserStack mainly for mobile device testing, and it provides us with brilliant test coverage across a full and broad range of mobile devices. I really appreciate the capability to test on iOS devices with our website UI, as the Safari browser can render page elements differently compared to Chromium-based browsers. This allows us to catch those issues much earlier and avoid defects in production systems. Not having access to iOS browsers or devices in our dev and test team is challenging, but BrowserStack reduces the need to purchase these devices. They have all the latest devices, so we don't have to worry about the purchase cost and maintaining older devices to ensure backward compatibility. Setting up BrowserStack was also straightforward, with no problems at all. Review collected by and hosted on G2.com.

It would be good if it was possible to run automated test scenarios across a number of devices and have a detailed report response. Also being able to automate a visual comparison between the ideal design and the rendered view. Review collected by and hosted on G2.com.

I like how BrowserStack makes cross-browser and cross-environment testing easy without needing to maintain our own infrastructure. It provides quick access to a wide range of browsers, operating systems, and device configurations, allowing us to validate our application behavior efficiently across multiple environments. I appreciate how well it integrates with our automation workflow, especially running Playwright-based end-to-end tests, helping us detect compatibility issues early in the development cycle. The debugging feature with logs, screenshots, and session recordings is really helpful for quickly identifying the root cause of failures. The tunneling capability is invaluable for testing local or staging environments not publicly accessible. Furthermore, integrating BrowserStack with Percy for visual regression testing allows us to catch unintended UI changes and maintain consistent design across releases. Overall, BrowserStack significantly simplifies cross-browser testing, improves the reliability of our testing process, and saves time by eliminating the need to manually manage multiple test environments. Review collected by and hosted on G2.com.

While BrowserStack is very helpful overall, there are a few areas where improvements could make the experience even better. Occasionally, test sessions can be a bit slow to start, especially when running multiple automated tests in parallel. This can slightly increase the overall execution time of our test suites. Another area that could be improved is the debugging experience for failed automation runs. While BrowserStack does provide logs, screenshots, and recordings, sometimes it takes a bit of time to navigate through the information to quickly identify the root cause of a failure. There are also times when certain browser or device environments may feel slightly slower compared to running tests locally. Improving performance and reducing latency during live debugging sessions would make the workflow smoother. Additionally, clearer insights or analytics around test failures and performance trends could help teams diagnose issues faster. Enhancements in reporting and easier ways to analyze failures across multiple runs would make the platform even more powerful for larger automation suites. Review collected by and hosted on G2.com.