HeadTidy Start free

Share a map. Plan it together.

Send one private link. The people you invite can view, comment or edit with you, and they do not need an account. You keep ownership, recovery and exports.

Create the narrowest useful link

Choose View when someone only needs to read, Comment for discussion, or Edit when they should change the map. Private links can expire, use a passcode and be revoked independently. Treat any active link like a password.

The real HeadTidy Share View with a read-only map fitted between its compact header and unobtrusive Make your own footer.
The public view keeps the same cards and connections as the app, while read-only status and the next step stay out of the map’s way.

Work on a map together

An Edit link covers the essential map workflow: move cards, add connected cards from the + handles, change titles and notes, delete a card with the cards under it, and add or replace images. The person you invite does not need an account. Every save is checked against the latest version, so a newer change is never silently overwritten.

See what changed

Comments attach to individual cards, and anyone who opens the link again sees what changed since their last visit.

Share the useful map, not a flattened preview

A shared map keeps notes, images, checklists, progress, links, tables and Dashboard widgets visible. View links preserve that context without editing controls; Comment and Edit add only the capability the owner chose.

Recover ordinary mistakes

Autosave checkpoints and the Vault provide a safety net for recent changes. Deleted maps and thoughts go through recoverable trash before permanent removal. Recovery complements, rather than replaces, your own backup.

Export without upgrading

Lossless JSON preserves HeadTidy data for backup and re-import. Markdown and OPML provide portable text and outline formats; PNG and PDF make a visual snapshot easy to share. Exports remain available on Free and Pro.

Sync is not the same as backup

Sync keeps devices aligned, including edits and deletions. A separate export protects against account loss, accidental changes and service failure. Keep periodic JSON exports for anything irreplaceable.