Documentation

Loft is 53 file-aware, formula-precise browser tools. Below is how the site works, what's shipped, what's next, and how to reach us.

For users

Install Loft as an app

Per-platform step-by-step install guide: Chrome, Edge, Safari on iOS / macOS, Android.

Offline mode & pinned tools

Pin tools for offline use. The dashboard's "About offline mode" panel explains what gets saved, where it lives, and how to keep it fresh.

What we collect (almost nothing), what stays on your device, and what we explicitly don't do.

Cookies & local storage

No tracking cookies. A breakdown of the first-party storage keys we use for offline pins, folder labels, and preferences.

Terms of service

Plain-language terms — what you can do with the tools, what we don't warranty, how disputes work.

About Loft Tools

The story behind the project, who builds it, and what makes the approach different.

Install diagnostics

Live capability report for the Install-as-app flow. If install isn't working for you, copy the report into a bug ticket.

User-facing release notes. Every notable feature, fix, or polish change since launch.

What's shipped, what's next, and what's being considered. Grouped Now / Next / Considering.

Feature requests

Vote on proposed tools and features. No account required; votes are de-duplicated via a privacy-preserving IP hash.

Tell us what tool you want. We'll triage and either build it, put it on the roadmap, or explain why not.

A form that files a labeled issue on our private tracker. Paste a diagnostics report if you have one — makes triage near-instant.

General feedback

Comments, ideas, hellos. Open-ended; we read all of it.

Support the project

How to sponsor Loft if you use it and want to help keep it free, local, and privacy-preserving.

For contributors — architecture decisions

Each decision doc captures why the codebase is shaped a particular way and what trade-offs were made. If you're planning a change that might conflict, read the relevant D-doc first.

For contributors — template patterns

Tools are built from a small set of reusable templates (calculator, converter, generator, file processor, text processor, comparison). Each pattern doc spells out the template's API, what kind of tool it fits, and the conventions to follow.