| | |

Playwright 21 ๐ŸŽญ Parallel Execution โ€” Workers, sharding, and –fully-parallel

โฑ๏ธ Estimated read: 10 min | |

As automated end-to-end testing suites grow from a handful of smoke tests into comprehensive verification layers covering hundreds or thousands of user scenarios, execution duration becomes a critical bottleneck for developer velocity. Running complex browser interactions sequentially across large codebases can stretch feedback loops past acceptable thresholds, turning routine pull request validations into hours-long waits. Playwright Test was architected from the ground up to solve this scalability challenge through a robust, multi-layered parallel execution model.

Mastering Playwright’s concurrency architecture requires understanding how isolated operating system worker processes distribute test files, how the fullyParallel configuration flag alters task scheduling granularity, and how test suite sharding horizontally distributes workloads across independent CI runner nodes. This chapter explores worker configuration limits, test-level parallelism, multi-machine sharding strategies, blob report merging, and best practices for eliminating shared state race conditions in high-performance test environments.

Key point: Playwright coordinates parallel execution across three distinct layersโ€”worker processes on a single machine, test-level scheduling via --fully-parallel, and horizontal sharding across multiple CI machinesโ€”to maximize performance and speed up feedback loops.

Why X exists

The sequential execution latency problem.

Running end-to-end browser workflows one after another forces fast network requests and UI interactions to queue idly behind lengthy synchronous test blocks, multiplying total test suite duration unnecessarily.

The test file boundary restriction.

By default, Playwright restricts file-level parallelization where distinct test files run on separate workers, but individual tests inside a single file execute sequentially, leaving multi-test files underutilized.

The shared mutable state race condition.

Executing multiple tests simultaneously over shared databases, global variables, or storage states creates unpredictable race conditions and flaky test failures unless proper test isolation mechanisms are enforced.

The CI/CD build time explosion challenge.

As applications expand, single-machine runners become CPU- and memory-bound, making it impossible to maintain fast continuous integration pipelines without distributing workloads horizontally.

The multi-machine scaling bottleneck.

Without a deterministic sharding strategy, splitting large test repositories across independent CI builder nodes results in uneven test distribution and idle runner threads.

The shard distribution imbalance risk.

Sharding test suites without test-level parallelism causes large files to cluster on single shards, creating severe performance bottlenecks where one runner finishes long before others.

a. Configuring Worker Processes and Resource Allocation

Playwright achieves parallelism on a single machine by spawning isolated operating system worker processes. Each worker runs as an independent process with its own dedicated browser instance, memory allocation, and isolated browser context, ensuring cookies, local storage, and in-memory variables do not leak between test cases.

TypeScript

// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  // Configure worker count based on environment (percentage string or fixed number)
  workers: process.env.CI ? '50%' : 4,
  
  // Set maximum test failure retries on CI workers
  retries: process.env.CI ? 2 : 0,
});

Bash

# Override worker count dynamically via the CLI
npx playwright test --workers=2

The workers configuration property accepts absolute numbers (e.g., 4), string percentages of available CPU cores (e.g., '50%'), or undefined to let Playwright auto-detect optimal core utilization. Restricting workers prevents resource thrashing and memory exhaustion on constrained local development machines or CI runners.

b. Unlocking Test-Level Concurrency with fullyParallel

By default, Playwright operates at Layer 1 parallelism: different test files run concurrently across available workers, but multiple tests inside a single file execute serially on the same worker. Enabling fullyParallel: true shifts scheduling granularity from files to individual test cases.

TypeScript

// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  // Enable test-level parallelism across all spec files globally
  fullyParallel: true,
  
  // Use 4 parallel workers for execution
  workers: 4,
});

TypeScript

// tests/catalog.spec.ts
import { test } from '@playwright/test';

// Opt out of fully parallel mode for a specific test group requiring serial order
test.describe.configure({ mode: 'serial' });

test.describe('Product Catalog Sequential Workflow', () => {
  test('step 1: seed catalog database', async ({ page }) => {
    // Serial dependency setup
  });

  test('step 2: verify seeded catalog items', async ({ page }) => {
    // Depends on step 1 execution order
  });
});

When fullyParallel is active, individual tests within a large spec file are broken down into discrete tasks that can be handed off to any available worker. For legacy or state-dependent suites, developers can use test.describe.configure({ mode: 'serial' }) to safely opt specific blocks back out of parallel execution.

c. Distributing Test Suites via CI Machine Sharding

When a test suite outgrows the capacity of a single physical or virtual machine, Playwright enables horizontal scaling across multiple independent CI nodes through test sharding. Sharding splits the total test suite into discrete, non-overlapping subsets using the --shard=x/y command-line argument.

YAML

# .github/workflows/playwright.yml snippet
jobs:
  test:
    name: Run Playwright Shards
    runs-on: ubuntu-latest
    strategy:
      matrix:
        shardIndex: [1, 2, 3, 4]
        shardTotal: [4]
    steps:
      - uses: actions/checkout@v4
      - name: Install dependencies & browsers
        run: npm ci && npx playwright install --with-deps
      - name: Run Playwright tests (Shard ${{ matrix.shardIndex }} of ${{ matrix.shardTotal }})
        run: npx playwright test --shard=${{ matrix.shardIndex }}/${{ matrix.shardTotal }}
        env:
          PLAYWRIGHT_BLOB_OUTPUT_DIR: blob-reports-${{ matrix.shardIndex }}
      - name: Upload blob report artifact
        uses: actions/upload-artifact@v4
        with:
          name: blob-report-${{ matrix.shardIndex }}
          path: blob-reports-*/

Because each shard executes independently on separate runner nodes, reporting tools receive fragmented test results. Playwright solves this by utilizing the blob reporter, which produces mergeable artifacts that can be combined post-execution into a unified HTML report.

Complete Example Session

TypeScript

// ============================================
// PART 1: PLAYWRIGHT CONFIGURATION SETUP
// ============================================
import { defineConfig } from '@playwright/test';

export default defineConfig({
  fullyParallel: true,
  workers: process.env.CI ? 2 : 4,
  retries: 1,
});

TypeScript

// ============================================
// PART 2: PACKAGE MANIFEST SCRIPT DEFINITIONS
// ============================================
export const packageScripts = {
  "scripts": {
    "test": "playwright test",
    "test:parallel": "playwright test --fully-parallel",
    "test:shard": "playwright test --shard=1/3"
  }
};

TypeScript

// ============================================
// PART 3: ISOLATED TEST DATA GENERATION PATTERN
// ============================================
import { test, expect } from '@playwright/test';

test.beforeEach(async ({ page }, testInfo) => {
  // Generate unique isolation identifiers per test run
  const uniqueToken = `user_${Date.now()}_${testInfo.parallelIndex}`;
  await page.context().setExtraHTTPHeaders({ 'x-test-user': uniqueToken });
});

TypeScript

// ============================================
// PART 4: CONCURRENT NAVIGATION SPECIFICATION
// ============================================
test('navigates to dashboard concurrently', async ({ page }) => {
  await page.goto('https://example.com/dashboard');
  await expect(page).toHaveTitle(/Example/);
});

TypeScript

// ============================================
// PART 5: WORKER-SCOPED FIXTURE SHARING
// ============================================
import { test as base } from '@playwright/test';

type WorkerFixtures = {
  dbConnection: string;
};

export const testWithDb = base.extend<{}, WorkerFixtures>({
  dbConnection: [async ({}, use) => {
    const conn = 'mock_db_cluster_connection';
    await use(conn);
    // Teardown after worker completes
  }, { scope: 'worker' }],
});

TypeScript

// ============================================
// PART 6: USING TESTINFO PARALLEL INDEX
// ============================================
testWithDb('partitions resource allocations', async ({ page }, testInfo) => {
  const workerSlot = testInfo.parallelIndex;
  expect(workerSlot).toBeGreaterThanOrEqual(0);
});

TypeScript

// ============================================
// PART 7: BLOB REPORTER CONFIGURATION FOR SHARDS
// ============================================
export const shardedConfig = defineConfig({
  reporter: [['blob', { outputDir: 'blob-report' }]],
});

TypeScript

// ============================================
// PART 8: REPORT MERGING SCRIPT UTILITY
// ============================================
import { mergeReports } from '@playwright/test';
import { resolve } from 'node:path';

async function combineShardArtifacts() {
  await mergeReports(resolve('./all-blob-reports'));
}

TypeScript

// ============================================
// PART 9: SERIAL OVERRIDE FOR DEPENDENT STEPS
// ============================================
test.describe('Payment Gateway Integration', () => {
  test.describe.configure({ mode: 'serial' });

  test('step A: tokenize credit card', async () => { /* ... */ });
  test('step B: execute charge using token', async () => { /* ... */ });
});

TypeScript

// ============================================
// PART 10: SESSION FINALIZATION
// ============================================
// Parallel execution, sharding, and worker orchestration validated successfully

Quick Reference

Parallel Execution Properties

PropertyTarget ScopePurpose
workersplaywright.config.tsControls worker process count (number, string percentage, or auto)
fullyParallelplaywright.config.tsEnables test-level concurrency within spec files
test.describe.configure({ mode })Test file scopeOverrides execution mode ('parallel' or 'serial')
--shard=x/yCLI flagDistributes test suites across multiple CI machines

Sharding and Reporting CLI Flags

Flag / ReporterAction Performed
--shard=1/4Executes shard 1 out of 4 total target shards
'blob'Outputs mergeable binary test results for CI shards
mergeReports()Programmatically combines multiple shard blob reports into one

Best Practices

โœ… Do This:

TypeScript

workers: process.env.CI ? '50%' : undefined                                 // โœ…

โŒ Don’t Do This:

TypeScript

workers: 32 // hardcoding high worker counts that choke CI resource limits  // โŒ

โœ… Do This:

TypeScript

const email = `testuser_${Date.now()}_${testInfo.parallelIndex}@test.com`;    // โœ…

โŒ Don’t Do This:

TypeScript

// share hardcoded database accounts across parallel test workers           // โŒ

โœ… Do This:

TypeScript

test.describe.configure({ mode: 'serial' });                                // โœ…

โŒ Don’t Do This:

TypeScript

// force entire test suites into serial mode when tests are fully independent // โŒ

โœ… Do This:

TypeScript

reporter: [['blob'], ['html']]                                              // โœ…

โŒ Don’t Do This:

TypeScript

// attempt to merge standard HTML reports generated across separate CI shards// โŒ

Common Pitfalls

PitfallWhy It HappensFix
Flaky database race conditionsMultiple concurrent workers attempting to insert records with identical primary keysUse timestamp prefixes or testInfo.parallelIndex to isolate test data
Uneven shard distribution timesSharding without fullyParallel: true, causing large test files to bottleneck single shardsEnable fullyParallel: true in your configuration file so Playwright distributes individual tests evenly
Missing test reports on CISharded jobs generating isolated HTML reports without combining them via blob reporterConfigure the blob reporter on shards and add a final aggregation step using mergeReports
CPU thrashing and memory crashesAllocating too many worker processes on a constrained CI virtual machineScale worker counts dynamically using percentage strings (e.g., '50%')

Real-World Examples

1. Configuring Dynamic Worker Allocation for CI Environments

TypeScript

export default defineConfig({
  workers: process.env.CI ? '50%' : 4,
});

2. Enabling Fully Parallel Test Scheduling Globally

TypeScript

export default defineConfig({
  fullyParallel: true,
});

3. Forcing Serial Execution on a Specific Dependent Suite

TypeScript

test.describe('Order Checkout Workflow', () => {
  test.describe.configure({ mode: 'serial' });
  test('cart addition', async () => {});
  test('payment processing', async () => {});
});

4. Executing Tests via CLI Sharding Arguments

Bash

npx playwright test --shard=1/4

5. Generating Blob Reports for CI Shard Aggregation

TypeScript

export default defineConfig({
  reporter: [['blob', { outputDir: 'blob-report' }]],
});

6. Using Parallel Index for Resource Partitioning

TypeScript

test('assigns unique worker bucket', async ({}, testInfo) => {
  const bucketId = testInfo.parallelIndex;
  expect(bucketId).toBeDefined();
});

7. Setting Worker-Scoped Database Fixtures

TypeScript

const test = base.extend<{}, { db: string }>({
  db: [async ({}, use) => {
    await use('connected_db');
  }, { scope: 'worker' }],
});

8. Overriding Worker Count via Command-Line Flags

Bash

npx playwright test --workers=2 --fully-parallel

9. Merging Sharded Blob Reports Programmatically

TypeScript

import { mergeReports } from '@playwright/test';
await mergeReports('./blob-reports-dir');

10. Limiting Retries on Flaky Parallel Workers

TypeScript

export default defineConfig({
  retries: process.env.CI ? 2 : 0,
});

Visual

Playwright Three-Tier Parallelism Architecture

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ TIER 3: Machine-Level (CI Sharding across N servers)   โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                            โ”‚
                            โ–ผ
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ TIER 2: Worker-Level (OS processes running in parallel)โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                            โ”‚
                            โ–ผ
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ TIER 1: Test-Level (--fully-parallel spec distribution)โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

File-Level vs. Fully Parallel Scheduling Flow

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ DEFAULT (fullyParallel: false): File 1 โ”€โ”€โ–บ Worker A    โ”‚
โ”‚ All tests in File 1 run sequentially on Worker A       โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ FULLY PARALLEL (fullyParallel: true):                  โ”‚
โ”‚ Test 1 โ”€โ”€โ–บ Worker A | Test 2 โ”€โ”€โ–บ Worker B              โ”‚
โ”‚ Individual tests distributed across available workers   โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

CI Sharding and Blob Reporting Pipeline

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ Shard 1 (Node 1) โ”€โ”€โ–บ Blob Report 1 โ”                   โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค                   โ”‚
โ”‚ Shard 2 (Node 2) โ”€โ”€โ–บ Blob Report 2 โ”ผโ”€โ”€โ–บ mergeReports() โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค                   โ”‚
โ”‚ Shard 3 (Node 3) โ”€โ”€โ–บ Blob Report 3 โ”˜                   โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                                     โ”‚
                                     โ–ผ
                     โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
                     โ”‚ Unified HTML Test Report      โ”‚
                     โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Summary

ItemValue
ConceptParallel Execution and Sharding in Playwright
Worker ModelIsolated OS processes with dedicated browser contexts
Concurrency FlagfullyParallel: true shifts scheduling from files to tests
Horizontal ScalingTest sharding via --shard=x/y command-line argument
Reporting StrategyBlob reporter ('blob') combined with mergeReports()
Isolation MechanismUnique test data generated via testInfo.parallelIndex
Serial Overridetest.describe.configure({ mode: 'serial' })
Resource ControlDynamic core percentage allocation (e.g., '50%')
Primary BenefitDrastically reduces test execution duration across CI pipelines
Best PracticeEnsure complete test data isolation to prevent race conditions

Key takeaways:

  • Leverage worker processes. Playwright automatically distributes test execution across isolated operating system worker processes to maximize CPU utilization.
  • Enable fully parallel mode. Set fullyParallel: true in your configuration to distribute individual tests within spec files across available workers.
  • Scale horizontally with sharding. Use --shard=x/y to distribute large test suites across multiple independent CI runner nodes.
  • Aggregate reports with blob reporters. Configure the blob reporter on sharded CI jobs and merge artifacts post-execution into a unified HTML dashboard.
  • Enforce strict data isolation. Prevent race conditions by generating unique timestamps and utilizing testInfo.parallelIndex for test data partitioning.
  • Control resource limits. Use percentage string worker allocations ('50%') to prevent resource exhaustion on constrained virtual machines.

Remember: Parallel execution and sharding transform bloated, time-consuming end-to-end test suites into high-speed verification pipelines. By combining worker optimization, fully parallel scheduling, and CI sharding, engineering teams can maintain rapid feedback loops without compromising test reliability.

Playwright Parallel Tests Tutorial

This video provides a helpful overview of configuring workers and sharding to scale Playwright test execution.

Was this helpful?


Stop using slow, ad-bloated tool sites! ๐Ÿคฎ

๐Ÿ”Ž Search “KandZ Tools” on Google to use many professional utilities for free.

KandZ.me is the ultimate minimalist hub for:
โœ… Finance (Mortgage, Interest, Inflation)
โœ… Tech (Base64, JSON, Dev Suite, IP)
โœ… Health (BMI, BMR, TDEE)
โœ… Productivity (Timer, Workspace, QR)

โšก๏ธ Fast & Private
๐Ÿ”’ No data leaves your device
๐Ÿ’Ž 100% Free

๐Ÿ”— Use it now: https://tools.kandz.me
๐Ÿ”– Bookmark itโ€”youโ€™ll need it later!