Free tools Windows power users keep installed
One-click scans. No signup required.
Connect your repository to Argos, run screenshot-producing tests in GitHub Actions, and upload the results for visual comparison on the pull request. For new GitHub Actions setups, enable Argos’s GitHub OIDC authentication and grant the workflow id-token: write; choose the Playwright or Storybook integration according to what you want to capture.
How the Argos and GitHub Actions connection works
Your workflow runs tests that render pages or components and produce screenshots. Argos receives those screenshots, compares them with the project’s baseline, and makes visual changes available for review through the pull request. You can approve expected changes or investigate and fix regressions. See the Argos documentation overview for the current product workflow.
1. Connect your GitHub repository to Argos
- Install or authorize the Argos GitHub App and connect the repository to an Argos project. The App lets Argos access the repository and report results on pull requests; confirm the current onboarding prompts and project settings in Argos.
- Decide which screenshots the workflow should capture: browser-tested pages with Playwright, component stories with Storybook, or screenshots already generated by a custom pipeline.
- Make sure the app or Storybook can be built and served in the Actions job as needed, and that screenshots are available to the integration or upload step.
2. Choose the screenshot integration
Playwright: capture browser-tested pages
Use this route when Playwright tests render the pages or user flows you want to compare. Argos’s Playwright guide uses @argos-ci/playwright, an Argos reporter, and the argosScreenshot helper in tests. Add the reporter to the test configuration and capture screenshots in the relevant tests. The guide’s workflow installs project dependencies and Playwright browsers before running the tests. See Argos’s Playwright and GitHub Actions guide.
The guide was published January 24, 2023. Its sample action versions and setup commands are examples from that date, not current version recommendations. Check the current GitHub Actions and Playwright documentation before copying pinned action versions or configuration.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Storybook: capture component stories
Use this route when the visual coverage should come from Storybook stories. Argos’s Storybook guide uses @argos-ci/storybook with @storybook/test-runner. In .storybook/test-runner.ts, the guide calls argosScreenshot(page, context) from the runner’s postVisit hook. The workflow builds Storybook, serves the generated storybook-static directory, waits for the local server, then runs the test runner and uploads the screenshots. See Argos’s Storybook and GitHub Actions guide.
This guide was published October 29, 2024. It shows a GitHub secret named ARGOS_TOKEN; for a new GitHub Actions setup, use the later OIDC guidance below where available rather than treating that older token example as the current default.
Custom screenshot output: upload an existing directory
If another tool already generates screenshots, you can use Argos’s Node.js SDK to upload a directory rather than adding a framework-specific screenshot helper. The SDK reference demonstrates upload({ root: "./screenshots", files: ["**/*.png"] }). It uses ARGOS_TOKEN when that environment variable is provided; this SDK detail does not mean every current GitHub Actions integration requires a long-lived secret. Check the Argos SDK reference and authentication guidance together when choosing how to authorize uploads.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
3. Configure GitHub Actions authentication
Argos’s May 11, 2026 guidance recommends GitHub OIDC for Actions uploads. Enable OIDC in the Argos project under Settings → Authentication, then grant the workflow the id-token: write permission so GitHub can issue an identity token. Argos verifies that GitHub-signed identity for the upload. When using OIDC, remove the long-lived ARGOS_TOKEN from the job.
Recommended Free Tools
Keep workflow permissions narrow. The cited authentication guidance specifies id-token: write for OIDC; retain or add other permissions only where your repository’s workflow or project setup requires them. Do not add broad write permissions just to upload screenshots.
Fork pull requests and tokenless fallback
GitHub may not issue an OIDC token for some runs, particularly pull requests from forks. Argos documents a tokenless fallback for those cases: it verifies the in-progress workflow run with GitHub before issuing a short-lived token. This lets the integration handle fork runs without relying on a repository-stored long-lived token. See Argos’s May 11, 2026 authentication announcement for the current details.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
4. Build the workflow around your app’s test surface
The exact workflow depends on your repository, runtime, package manager, and test configuration. Use this sequence as a checklist, then adapt it to the corresponding Argos framework guide and your existing workflow:
- Check out the repository and set up the required runtime.
- Install dependencies from the repository’s lockfile—for npm projects, the older Playwright example uses
npm ci. - Install required browser binaries and system dependencies for Playwright, or build Storybook if capturing stories.
- Start or serve the app if your tests need a running site. For Storybook, serve the built output and wait until the local server is ready before starting the runner.
- Run the screenshot-producing Playwright tests or Storybook test runner. Keep screenshot generation and upload in the same job, or explicitly transfer the screenshot files to the upload step.
- Ensure the job has the OIDC permission and that OIDC is enabled in the Argos project.
Argos’s older Playwright workflow runs npm exec playwright test after installing dependencies and browsers. Its Storybook example builds and serves Storybook before running the test runner. Treat these as integration patterns, not copy-and-paste guarantees for a repository with different scripts or current action versions.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →5. Review visual changes on the pull request
After the workflow finishes, open the Argos result or check associated with the pull request. Compare changed screenshots with the baseline. Approve changes that are intentional; if a difference is unexpected, use the diff to locate the affected page or component and correct the underlying issue before merging.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Common problems and fixes
- Upload authentication fails: confirm OIDC is enabled in the Argos project’s Settings → Authentication and that the workflow has
id-token: write. If the run is from a fork, GitHub may not provide OIDC; Argos documents a tokenless fallback, so check the run logs and current Argos authentication guidance before adding a long-lived secret. - The job runs but Argos has no screenshots: confirm the test actually invokes the Argos capture helper or reporter, or that the SDK upload points to the directory and file pattern where screenshots were generated. Ensure screenshots are in the same job or transferred to it.
- Storybook tests cannot reach the preview: ensure the build completed, the generated directory is being served, and the workflow waits for the local server before starting the test runner.
- Playwright cannot launch a browser: install the browser binaries and system dependencies required by the project’s Playwright setup before running visual tests.
- The workflow uses outdated examples: the cited Playwright guide dates to January 2023 and Storybook guide to October 2024. Verify action versions, package compatibility, and authentication against current documentation rather than assuming the sample versions remain current.
- A pull request shows unexpected visual diffs: compare the changed screenshots with the baseline and determine whether the change is intentional. Approve expected changes; otherwise fix the page or component and rerun the workflow.
Performance, reliability, and cost considerations
Visual jobs depend on the app starting reliably and screenshots being captured under repeatable conditions. Keep the build, server readiness check, browser setup, and capture step explicit so a missing screenshot is distinguishable from an application or browser failure. For a custom pipeline, upload only the intended screenshot files by using a specific root directory and file pattern.
The cited Argos integration guides and documentation overview do not establish a universal runtime, pricing figure, or screenshot limit for this workflow. Check the current Argos project and plan details for the account you use rather than assuming a rate or allowance from the integration examples.
Or skip the browser setup
If you need a screenshot endpoint rather than a visual-regression baseline workflow, ScreenshotNeo is a website screenshot API and MCP server. A GET request with a URL returns an image or PDF; it is not a replacement for Argos’s baseline comparison and pull-request review.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
For a standalone screenshot in a workflow, store an API key as a GitHub Actions secret and pass it as an environment variable rather than putting it directly in the command:
curl -G "https://api.screenshotneo.com/v1/shot"
-d access_key="$SCREENSHOTNEO_API_KEY"
--data-urlencode url=https://stripe.com
-o shot.webpSee the ScreenshotNeo API documentation for request options. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
