Browser Kitty is a collection of small tools that run in the browser. No account or installation is required. Tools are designed to process user files and data locally whenever their documented behavior allows it.
Browse all apps · Health snapshot · Live health · Feature requests
This repository is the public app registry, health-check hub, and feedback entry point for Browser Kitty. Each application remains in its own public repository; this repository is not a monorepo and is not a runtime dependency of the website.
You do not need to find the individual app repository before sending feedback. Start here and the issue can be routed to the right place if needed.
| I want to… | Link |
|---|---|
| Improve an existing tool | Feature request |
| Suggest a new browser tool | New tool idea |
| Report something broken | Problem report |
| See existing requests | Issues |
| Use the tools | browser-kitty.com |
If Browser Kitty is useful to you, starring this repository is a simple way to show interest in the project. Stars and issue reactions are also useful signals when deciding which tools or improvements to work on next.
The source of truth for application code is each individual app repository. This parent repository manages the cross-app information needed by Browser Kitty:
apps.json— application registrycategories.json— shared category definitionsgenerated/apps.public.json— deterministic build-time export for the Browser Kitty website- repository inventory, asset, Pages, release, and runtime checks
- consolidated health reports
- release-readiness checks
Current inventory: 105 registered applications, including 100 listed on Browser Kitty across 7 categories and 5 not yet listed there. Of the 100 listed apps, two are still labeled development and one release candidate. Catalog inclusion does not itself certify stable release readiness; per-app limitations remain in effect.
browser-kitty.com
↑
| build-time data
generated/apps.public.json
↑
apps.json + categories.json
|
+---- repository health checks ----> htmlapps-* repositories
The Browser Kitty website consumes the public export at build time. Browser clients do not fetch this registry at runtime.
| Repository | Role |
|---|---|
browser-kit |
Private Browser Kitty website source |
browser-kitty-apps |
Public registry, health checks, automation, and feedback hub |
htmlapps-template |
Public application template |
htmlapps-* |
Public source repositories for individual applications |
Feedback, documentation fixes, registry corrections, and automation improvements are welcome. See CONTRIBUTING.md.
For changes to an individual application's implementation, the corresponding app repository is normally the best place for the code change. If you only know the Browser Kitty tool name, opening an issue here is fine.
Security-related reports should follow SECURITY.md. Do not attach private or sensitive files to a public issue.
{
"id": "ffmpeg-filter-builder",
"name": "FFmpeg Filter Builder",
"nameJa": "FFmpeg Filter Builder",
"repository": "ttomohisa/htmlapps-ffmpeg-filter-builder",
"category": "video",
"status": "stable",
"browserKitty": {
"published": true,
"slug": "ffmpeg-filter-builder"
},
"release": {
"version": "1.2.3"
},
"pages": {
"url": "https://ttomohisa.github.io/htmlapps-ffmpeg-filter-builder/"
}
}See REGISTRY_SPEC.md for the complete schema and policy.
PowerShell 7 is used for repository validation:
./scripts/check-powershell.ps1
./scripts/check-registry.ps1
./scripts/generate-public-export.ps1 -Check
./scripts/check-release-candidate.ps1Cross-repository health checks can also be run individually:
./scripts/check-repositories.ps1
./scripts/check-assets.ps1
./scripts/check-pages.ps1
./scripts/check-releases.ps1
./scripts/check-runtime.ps1
./scripts/generate-report.ps1GitHub Actions runs the same checks on changes and on the scheduled health workflow. WARN keeps maintenance debt visible without blocking the workflow; a blocking FAIL makes Repository Health fail.
generated/apps.public.json contains only published, website-safe registry fields. It is derived from apps.json and categories.json and must not be edited manually.
After changing registry data:
./scripts/generate-public-export.ps1
./scripts/generate-public-export.ps1 -Check| Document | Purpose |
|---|---|
| OPERATIONS.md | Production operation and maintenance |
| REGISTRY_SPEC.md | Registry schema and policies |
| RELEASE_CHECKLIST.md | Release-readiness checklist |
| reports/README.md | Health report behavior |
| standards/BROWSER_KITTY_GUIDE.md | Shared Browser Kitty app guidance |
| CATALOG.md | Human-readable application catalog |
| STATUS.md | Human-readable Repository Health snapshot |
| CHANGELOG.md | Version history |
v1.2.0 reconciles the registry against the 100 tools actually listed on Browser Kitty. It adds four missing applications (Audio to MIDI, Best Shot Picker, Pause & Tell, and Reverse Clip), corrects six publication flags, and mirrors four current child versions. The resulting inventory has 105 apps: 100 listed and 5 not listed. Three listed applications explicitly retain development/RC maturity and now generate a visible registry readiness warning instead of being silently relabeled stable. Public export and catalog data have been regenerated. STATUS.md remains a timestamped health snapshot; use live Repository Health for the current check.
v1.1.5 mirrors 87 current child-repository versions, reconciles four publication flags against the live Browser Kitty catalog, and adds five independently hosted applications as unpublished inventory entries. The registry now contains 101 apps: 90 catalog-published and 11 unpublished. Development entries retain their documented release limitations; child versions remain independent of the separately deployed website.
v1.1.4 mirrors Pop-up Face Check-in v1.0.3 and marks PDF Organizer and Temporary Links as stable after their metadata modernization. It regenerates the public export and catalog while preserving inventory, publication flags, and runtime capabilities.
v1.1.3 reconciles child versions and metadata after the repository warning cleanup and regenerates the public export and catalog. The inventory stays at 96 apps, with 86 published and 10 outside the Browser Kitty catalog. Child releases remain independent from the separately deployed Browser Kitty website.
v1.1.2 makes repository health evidence more precise: per-asset execution context distinguishes main-thread modules from Workers; explicit unversioned apps have no fabricated version comparison; declared output aliases remain visible. Regression tests protect real Worker, WASM, and version warnings. See CHANGELOG.md.
v1.1.1 refreshes current child-repository versions and reconciles the registry with the live Browser Kitty catalog: 96 registered apps, 86 published apps, and 10 independently hosted apps outside the catalog. It corrects two catalog slugs, retains stable registry IDs, and regenerates the public export and catalog. Mirrored app versions describe child repositories, not the version currently bundled by the separate Browser Kitty site. See CHANGELOG.md for the release history.
v1.1.0 adds human-readable views for the registry and Repository Health. CATALOG.md is a deterministic catalog generated from the registry, while STATUS.md is a health snapshot; every Repository Health run regenerates the status view and publishes it directly in the GitHub Actions Job Summary. See CHANGELOG.md for the full release history.
MIT License. See LICENSE.