Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is catonmat.net?
catonmat.net is the personal blog of Peteris Krumins, and the page in question is a post announcing a redesigned user interface for Browserling, his browser-testing service. In other words, the site itself is a blog about programming, command-line tools and software projects, while this particular page documents a product update rather than offering a general introduction to the site.
What the page covers
- An announcement of a new, single-menu interface for Browserling
- Menu controls for choosing an operating system and browser version
- A URL field for loading a site directly in the chosen browser
- Display options for zooming and changing resolution, including responsive testing
- Screen capture with annotation tools such as pen, rectangle, text and eraser
- Additional features listed: local testing via an SSH tunnel to localhost or a local network, an on-screen keyboard, sharing a browser link, and sending feedback
Who it is useful for
The post is aimed at people who already use or are curious about Browserling: web developers checking how a site renders across browsers, testers who need a quick screenshot with annotations, and anyone who wants to try a site on a platform they do not have locally. A reader who only wants to understand what catonmat.net is will find the broader blog more relevant than this single announcement.
A practical next step
If cross-browser checking is your goal, open the linked Browserling session described in the post and try the workflow end to end: pick an operating system and browser, load your own site through the URL field, change the resolution to a mobile width, then capture and annotate a screenshot. That sequence exercises most of the features the post describes and shows quickly whether the tool fits your testing routine. For related browser-based testing options, see BrowserStack and LambdaTest.
How do I test my website on different browsers using catonmat.net's Browserling tool?
Open catonmat.net and use the Browserling link there to start a session in a specific browser, then test your site directly inside that remote browser. The tool's own interface is built around one menu: pick the platform and browser at the top, enter your URL, and use the feature buttons at the bottom for display, screenshots, and local testing.
A practical test flow
- Choose the target. In the menu, select the operating system and browser version you want to check, such as an older Chrome, Firefox, Safari or Edge. Loading a version takes a click or two.
- Enter your URL. Type your site's address into the URL navigation field and click go; the browser opens and loads the page.
- Resize and zoom. Use display options to change the resolution and zoom level. This is how you check responsive breakpoints and how the site looks on a 4K screen, a small laptop, or a phone-sized viewport.
- Repeat across browsers. Work through the browsers your audience actually uses, noting layout breaks, font differences, and JavaScript errors each time.
- Capture what you find. The screen capture feature takes a screenshot of a selected browser region, then lets you annotate it with a pen, rectangle, text, or eraser before sharing it with a developer or client.
- Test local or private pages. If your site isn't public yet, the local testing feature opens an SSH tunnel to localhost or your local network so the remote browser can reach it. The on-screen keyboard helps when you're on a non-English keyboard or a mobile device, and "share a browser" sends someone a link to the current browser and page.
Deciding when this fits
Browserling is a hosted browser service, so it suits quick cross-browser checks, client demos, and verifying a page on a browser you can't install locally. It's less suited to automated regression suites or debugging that needs deep access to your own machine's dev tools and network stack — for those, a local setup or a dedicated testing framework is usually a better fit. Also keep in mind that a remote session renders your site on the service's infrastructure, so network conditions and geolocation may not match your users'.
A useful next step: list the browser/OS combinations from your analytics, test the top three first, and capture annotated screenshots of any breakage so the fix is unambiguous.
Can I use catonmat.net to test a local website running on my computer?
Yes, but not by pointing the browser directly at your own localhost. The page evidence describes a local testing feature in the new Browserling interface that "allows opening an ssh tunnel to localhost or local network to test local websites." That is the intended path: the remote browser reaches your machine through a tunnel rather than you running the browser locally.
What that means in practice
If you are building a site on http://localhost:3000 and need to see it in a specific browser or platform, you would:
- Start your local server as usual.
- Open the Browserling interface and load the browser/platform you need.
- Use the local testing feature to open the tunnel to localhost or your local network.
- Navigate to the local address and test.
Limits worth knowing
- The tunnel is the mechanism, not a general "open my localhost" button, so expect a setup step rather than typing
localhoststraight into the URL field. - Local testing is described as one of the features in the menu, alongside display options, screen capture, on-screen keyboard, and sharing a browser link. The page does not detail tunnel setup requirements, supported ports, or whether it works behind restrictive corporate networks, so treat those as things to verify before relying on it for daily work.
- For quick local iteration, a browser already installed on your machine is simpler. The remote-browser route makes more sense when you specifically need a browser or platform you do not have locally.
A useful next step
If your goal is cross-browser checking of a site you are actively developing, try the tunnel once with a trivial page first. That tells you whether your network and firewall cooperate before you depend on it during a deadline. For related browser-testing options, BrowserStack and LambdaTest also offer hosted real-browser testing with local-connection features, and catonmat.net itself is the blog where this interface change was announced.
How do I take and edit screenshots of a browser session on catonmat.net?
You take screenshots through Browserling's capture-screen feature, not through catonmat.net itself. The blog post on catonmat.net describes the tool: after selecting the browser region you want, it opens the screenshot and gives you editing tools including a pen, rectangle, text annotation and eraser.
A practical workflow
- Open the page you want to capture in a Browserling browser session.
- Use the menu's capture-screen feature and select the region of the browser to save.
- Annotate the captured image with the pen, rectangle, text or eraser tools.
- Copy the result to your clipboard or save it, depending on the options shown.
The same post also mentions display options that let you zoom and change the browser resolution. That matters for screenshots: if you're on a 4K monitor, zooming in before capturing avoids tiny, unreadable text, and resizing the viewport lets you capture the same page at different screen sizes for responsive testing.
Who this suits
This is most useful for developers and QA testers who need to document a bug or show a layout problem in a specific browser version. The annotation tools are the point — a plain screenshot rarely explains what's wrong, while an arrow or a text label on the broken element does.
If you only need a local screenshot on your own machine, your operating system's built-in capture tool is faster. Browserling's advantage is capturing a remote browser session on a platform or browser version you don't have installed. For a broader look at cross-browser capture tools, see Browserling.
Next step
Open a session at a browser version you actually need to test, resize to the viewport you care about, then capture and annotate.
Is there a way to simulate different screen sizes for responsive design testing on catonmat.net?
Yes — but not as a design tool on catonmat.net itself. The relevant capability lives in Browserling, the browser-testing service whose new interface is described on catonmat.net. The post's "Display options" feature explicitly supports zooming the browser and changing the resolution to a larger or smaller one, and the page states this lets you do responsive web testing by seeing how a website looks at various screen sizes.
How it fits a responsive-testing workflow
For a concrete scenario: you have built a page and want to check it at a narrow mobile width, a mid-size tablet width, and a wide desktop width without switching physical devices. You would open the site in a Browserling browser session, use the display options to adjust resolution and zoom, and observe the layout at each size.
- Resolution changes approximate different viewport sizes, which is the core of responsive checking.
- Zoom helps on high-density displays, such as a 4K monitor, where the browser may otherwise render uncomfortably small.
- Screen capture pairs with this: you can capture a region of the session and annotate it with a pen, rectangle, text, or eraser, which is handy for sharing a layout issue with a developer or client.
What to keep in mind
The page describes resolution and zoom controls, not a named device-preset list, so treat it as manual viewport testing rather than a drop-in replacement for a device-emulation panel. If you need precise breakpoint debugging, browser developer tools or a dedicated responsive-design checker may give finer control; Browserling's strength here is testing real browser and platform combinations at chosen sizes. For a quick cross-browser sanity check of a layout at several widths, the display options described on catonmat.net are a practical route.
Next step: open a session in the browser you care about and step through your site at your three or four key breakpoints, capturing annotated screenshots of anything that breaks. For related reading on the same site, see catonmat.net.
Can I share a live browser session with someone else using catonmat.net?
Yes. The page evidence for catonmat.net describes a "share a browser" feature in the Browserling interface that "allows sending a quick link to the current browser and website you're viewing." So rather than describing a screen recording or a static screenshot, the site presents this as a way to hand someone a link into the same browser session you have open.
H3 How it fits into a real workflow A common case: you're testing a checkout flow and hit a bug only you can reproduce. Instead of writing a long description ("click the third tab, then resize the window"), you'd send the link so the other person sees the same browser and page. The same applies to pairing with a developer, walking a client through a layout, or showing a colleague a responsive breakpoint you're questioning.
H3 Things to consider before relying on it
- It is a link, not a co-editing tool. The evidence says it sends a quick link to the current browser and website. It doesn't state that two people can control the browser at once, so treat it as a hand-off or a shared view rather than Google-Docs-style collaboration.
- Session lifetime matters. A quick link is convenient precisely because it's low-friction, but links like this are often time-limited or tied to the session. If the other person needs to keep working after you close the tab, check whether the browser stays alive.
- Sensitive pages. If the session is logged into a staging account, an internal admin panel, or anything with customer data, sharing the link shares that access. Prefer a test account, and revoke or close the session when you're done.
- Related features on the same page. The interface also lists screen capture with annotation tools, local testing via an SSH tunnel to localhost, and an on-screen keyboard, which cover adjacent needs: capture for async feedback, sharing for live feedback.
H3 Practical next step Open the browser and page you want to share, then look for the share option in the menu's feature area and copy the link it produces. Before sending it, open the link yourself in a private window while logged out, so you see exactly what the recipient will get. If the recipient needs to keep the session after you leave, confirm that first; if they only need to see a specific state, a screenshot from the capture feature may be the safer choice.
User reviews (0)