Community-built developer & QA toolkit

WebForge Toolkit

A non-commercial, contributor-led browser workspace created to help developers and QA professionals inspect webpages, troubleshoot requests, transform data, analyze HTTP archives, and test user-selected web endpoints.

Community purpose

Built to help the developer and QA community

WebForge Toolkit is a non-commercial community initiative maintained by contributors who want everyday web development and quality-assurance work to be more accessible, efficient, and understandable.

Help before commerce

The project supports practical problem-solving, learning, and knowledge sharing. It is not designed for advertising, lead generation, or selling user data.

Responsible professional use

The tools are intended for developers, QA engineers, learners, and authorized reviewers working on systems they own or have permission to test.

Core capabilities

One focused workspace for web development and QA

WebForge combines local data utilities with user-triggered page inspection and browser-compatible clients. Features run locally unless the user explicitly contacts a selected endpoint.

Observe

Network Inspector

Inspect methods, status, timing, size, generated cURL, and available Fetch/XHR response bodies.

Transform

Data Formatters

Format and validate JSON/XML and convert CSV, TSV, Excel-paste data, and JSON.

Analyze

Page & HAR Analysis

Review performance, accessibility, storage, CSP/CORS, links, tables, and HTTP archives.

Export

Page & Asset Export

Generate Markdown, text, PDF, image galleries, JSON, and CSV from user-selected pages.

Develop

Local Developer Tools

Work with JWT, URLs, hashes, HMAC, Base64, regex, diffs, timestamps, and secure values.

Connect

Browser-Compatible Clients

Test REST, GraphQL, SOAP, WebSocket, SSE, MQTT, Elasticsearch, OAuth/PKCE, and web gateways.

Privacy posture

Designed for explicit, user-controlled workflows

No WebForge backend

There is no analytics service, advertising SDK, remote code, or WebForge-operated data server.

Direct endpoint access

Network requests leave Chrome only when a user runs a link check, opens OAuth, or connects to a destination they selected.

Project contacts

Credits & support