Anchorify V2: every file type, every interface
V2 is live. Quick tour of what is new.
More content types, rendered properly. Markdown was the original
target. V2 adds first-class renders for code (with syntax highlighting),
JSON, YAML, CSV, TSV, and raw HTML. Drop a .csv on the CLI and you get
a table on the page, not a wall of commas. See content types
for the full list and how detection works.
Explicit render-type selector. Filename-based detection is still the
default, but you can override it from the /new page or via the API.
Useful when you want to share a .txt that is actually JSON, or render
a markdown file as plain code for review.
Public vs secret. Shares default to secret — noindex headers, no
search engines. Flip one to public when it is meant to be discovered.
The setting is per-share and changeable from the dashboard.
Password protection. Optional per share. Visitors hit an unlock screen, enter the password, then see the content. Useful for client work where the URL might forward further than you expected.
Comments and reactions. Anyone with the URL can read. Signed-in viewers can leave comments or react with emoji. The owner sees everything in the dashboard.
Per-visitor analytics. The dashboard surfaces a breakdown of unique visitors per share — first-view date, total hits, agent class. No third-party tracker, no cookies on the public page.
REST API and CLI parity. Anything the CLI does is now a documented REST call. See the API reference. Mint a per-user token from the dashboard and you are off.
If you have been using Anchorify since the early bearer-token days, nothing breaks — your shares keep their URLs and the legacy token still works for writes. See the getting started guide for the new flow.