
How to Password-Protect a Page and Pick Its Link
Two Pro options on the publish panel — a custom link and a password — turn a random dochost URL into dochost.co/d/team-handbook that only people with the password can read. Here is the flow end to end, including what readers see.
By default a published page gets a random slug (dochost.co/d/2d5uzqiq) and anyone with the link can open it. The publish panel has two optional fields that change both: Custom link lets you choose the slug, and Password protect puts a password prompt in front of the page. Both are Pro features. This guide walks through publishing a page with both set, then shows exactly what a reader sees.
Fill the two optional fields
On the homepage, switch to Paste Code (or drop a file), paste your Markdown or HTML, and scroll to the bottom of the panel:
- Custom link (optional) — type the slug you want after
dochost.co/d/. Three to thirty-two characters: lowercase letters, numbers and hyphens, no leading, trailing or doubled hyphens. If it is taken, reserved, or contains a word we block (brand, banking and sign-in terms), the field tells you before you publish. - Password protect (optional) — type the password readers will need. Anything goes; it is hashed before it is stored and never shown again.
- Pick Private under Visibility. A password-protected page can technically be listed on Explore, but there is rarely a reason to advertise a page people cannot open.
- Click Get my link.

The success panel shows the link you chose, not a random one:

What readers see
Anyone who opens the link gets a plain gate before any content loads — no title, no preview, no dochost branding to work around:

After Unlock, the page renders normally. The unlock is remembered in that browser with a short-lived cookie, so a reader is not asked again on every visit, but the cookie never leaves the page's own host.

A wrong password just says Wrong password — try again. There is no lockout, but attempts are rate-limited, and the page body is never sent to the browser until the password is right — the gate is enforced by the server, not hidden by a script.
Things worth knowing
- The password is set when you publish. The page's manage screen shows whether protection is On or Off under Page settings, but there is no field to change it there. To change or remove a password, republish the page — the edit flow keeps the same slug.
- Custom links are permanent for that page. If you delete the page, the slug is freed and someone else can take it.
- Search engines and Explore. A protected page is never indexed — the gate is all a crawler sees. Keep Visibility on Private too, or the title will still appear on Explore.
- The MCP tools support both. From Claude, ChatGPT or Cursor,
publishacceptscustomSlugandpasswordon Pro, so "publish my Q3 report as a private page with a password" does the same thing without opening the site.

On the free plan
The same two fields are on the panel, marked Pro. Typing in one opens a short upgrade card that keeps your draft — nothing you pasted is lost — and Publish free instead publishes the page without the option.

Pro is from $4.92 a month billed yearly and also makes every link permanent; see pricing.
更多文章

Google Docs 'Publish to the Web' vs dochost: Sharing a Document as a Link
Google Docs has a built-in publish button, so when do you need anything else? An honest comparison for turning a formatted document into a shareable URL.

How to Turn a Claude Artifact Into a PDF
Claude has no export-to-PDF button, and printing from the chat prints the conversation instead. Here's the route that actually produces a clean PDF of the artifact itself.

How to Publish a README as a Webpage
Turn a README or any repo Markdown into a clean, shareable webpage in one paste — no repo access, no GitHub Pages setup, and no build step needed.
邮件列表
加入我们的社区
订阅邮件列表,及时获取最新消息和更新