# Typr

Typr is a local-first, browser-based workspace for writing and previewing Typst, LaTeX, and Markdown documents. It is open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/3425/typr

## Description

Typr is a local-first, browser-based workspace for writing and previewing Typst, LaTeX, and Markdown documents. Projects are stored in browser storage on your device and reopen offline, so it needs no appdata volume. Aimed at self-hosters who want personal typesetting without installing a toolchain on every computer, it is intended for trusted local network (LAN) or virtual private network (VPN) use; never expose it publicly.

## Platform availability

Available on 1 of 10 platforms: Unraid.

## Health score

52/100 (Fair), based on 4 of 4 factors.
- Maintained: 94 (last commit 88 days ago)
- Popular: 12 (3 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)
- Light to run: 30 (4 GB minimum RAM)

## Links

- GitHub: https://github.com/max-prime-math/typr
- Official website: https://typr.ca
- Unraid: https://ca.unraid.net/apps/typr-0f0gg870q69n3f?q=Typr

## Common questions

### Do self-hosted Typr projects need a Docker volume or appdata folder for user data?

No, self-hosted projects are kept in browser storage on the device by default, so there is no appdata volume to mount.

### Is Typr Server required for basic writing and preview?

No, a fresh self-hosted browser profile works without Typr Server and makes no Typr Server or mapped-workspace requests. You can add it later by entering its URL under Settings > Editor > Typr Server.

### Can I expose self-hosted Typr behind a public reverse proxy?

No, self-hosted Typr and Typr Server are unauthenticated trusted-environment services. Run them only on a trusted machine, LAN, or private VPN, and never expose them to the public Internet.

### How should I host the Development, Beta, and Stable release channels?

Each channel must be a separately named PWA on a distinct origin so their service workers and offline caches cannot control one another. GitHub Pages supports only one Pages site per repository, so independent channel deployments need separate Pages repositories/sites or branch subdomains.

---
Source: Our Local Host (https://ourlocalhost.com/app/3425/typr), the self-hosted and open-source app directory.
