# Request a feature

> Describe a tool or capability you need and it gets built — small changes often the same day, bigger ones in a few days. Free, no account.

Submit an email address plus a plain-English write-up of what you want. The page estimates the build time from the description as you type and every request gets a reply from a human.

## How long things take

- A few hours (often same day): a focused change to something that already exists — a new option, a remembered setting, a keyboard path.
- About a day (24-48 hours): a self-contained addition to an existing desk, such as a new export format or converter.
- A few days (3-5 days): new engine work, a new tool surface, or an on-device model.
- Scoped together: larger product ideas, answered within a day with a plan for what to build first.

## Constraints worth knowing

SafePaper has no user accounts and never sends file bytes to a server, so requests that assume a login, cloud sync, or server-side processing get reshaped rather than rejected — usually into encrypted on-device storage, peer-to-peer transfer, or a bring-your-own S3/R2 bucket.

The request form is the only place on SafePaper that sends typed text to a server. It accepts an email address, a write-up, and a workspace id. It never accepts files.

Discord (for conversation instead): https://discord.gg/uNaZ5nBcuj

---

Canonical HTML: https://www.safepaper.app/request-a-feature
Markdown: https://www.safepaper.app/request-a-feature.md

There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check.