---
title: "Discussion on \"Building ToolVerve: How I Built a 100% Client-Side Web Utility Suite (64+ Tools) in 30 Days\" | Hashnode"
description: "Discussion on \"Building ToolVerve: How I Built a 100% Client-Side Web Utility Suite (64+ Tools) in 30 Days\". How I built ToolVerve a privacy-first suite of 64+ free, browser-native web tools running on React, WebAssembly, and with zero server uploads."
url: "https://hashnode.com/posts/building-toolverve-how-i-built-a-100-client-side-web-utility-suite-64-tools-in-30-days/6a9d3a533cd1d6d7cf41c757"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building ToolVerve: How I Built a 100% Client-Side Web Utility Suite (64+ Tools) in 30 Days](https://toolverve.hashnode.dev/building-toolverve-how-i-built-a-100-client-side-web-utility-suite-64-tools-in-30-days?utm_source=hashnode&utm_medium=feed)

How I built ToolVerve a privacy-first suite of 64+ free, browser-native web tools running on React, WebAssembly, and with zero server uploads.

Sep 6 · 2 min read · toolverve.hashnode.dev  
Read the article

-   [#webdev](https://hashnode.com/tag/webdev)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#reactjs](https://hashnode.com/tag/reactjs)
-   [#wasm](https://hashnode.com/tag/wasm)
-   [#privacy](https://hashnode.com/tag/privacy)

## Written by

[Muhammad Abdullah Sattar](https://hashnode.com/@abdullahsattar)

@abdullahsattar · Pakistan

  
[View profile](https://hashnode.com/@abdullahsattar)

Self-Taught Builder | Building Privacy-First Web Utilities with React & AI

English Lit student building web apps. Creator of ToolVerve (toolverve.com) — a privacy-first suite of 64+ browser-native web utilities built with React, WebAssembly, and AI.

## Responses 2

Markdown supported · ⌘↵ to post

[Mark Reeves](https://hashnode.com/@mreevestools)

[Sep 28](https://hashnode.com/posts/building-toolverve-how-i-built-a-100-client-side-web-utility-suite-64-tools-in-30-days/6a9d3a533cd1d6d7cf41c757/comment/6abac6c9cfa7954a39eb8734)

64 tools in 30 days is a brutal pace - that's a tool every 11 hours including sleep. the 100% client-side constraint probably saved you, no backend to babysit. what broke most often at that speed, the tools themselves or the shared scaffolding?

[Muhammad Abdullah Sattar](https://hashnode.com/@abdullahsattar)

[Sep 28](https://hashnode.com/posts/building-toolverve-how-i-built-a-100-client-side-web-utility-suite-64-tools-in-30-days/6a9d3a533cd1d6d7cf41c757/comment/6abac6c9cfa7954a39eb8734#reply-6abac876295f9f64c99a33e9)

Thanks! You're totally right .Making everything run 100% in the browser without a backend saved a ton of time. And the catalog has actually expanded to 96+ tools now! ​To be honest, I built this using Google Antigravity (AI) to generate and manage the code, so I wasn't typing out every tool line-by-line by hand! ​Even with AI, the main site scaffolding broke the most at first. Whenever we updated shared things like the header or site layout, it would accidentally break older tool pages. Once we created a strict, fixed template for the tools to follow, scaling up became much smoother!
