You have something to say and you want it on the open internet — not buried in a chat thread, not stuck in a draft folder. Textpad.cloud is the most direct path from "I have a thought" to "here is the link." This guide walks you through it from zero.

Open Textpad

Go to textpad.cloud. The homepage is a blank editor. There is no login screen between you and your first sentence — that is by design.

Write a title

Type your title at the top. Keep it descriptive — the title is what people see in search results, share previews, and your own future archive. Treat it like a promise to the reader.

Write your post

Hit return and start writing. Use headings to break up sections. Use lists for steps or comparisons. Use code blocks for code. The editor handles the markup so you can focus on the words.

Add an image (optional)

Paste any screenshot or drag in any image. Textpad uploads it, embeds it, and gives it a stable URL. No image-hosting setup.

Share the URL

At the top of the page is the URL of your post. Copy it. Paste it into Slack, Twitter, an email — wherever your readers live. You just published.

Come back tomorrow

Your post is saved. Your archive is building. When you are ready to claim a handle and make this your blog, do that — but only when you want to. There is no countdown.

Welcome to publishing

That is the whole loop. Write, share, repeat. The tools that get out of your way are the ones you actually use; the ones you actually use are the ones that change how you think. Textpad is built for both.

A private blog is not a smaller public one — it is a different medium with a different reader. The audience is narrow, the trust is high, and the obligations are different. Here is what we have learned about writing for it well.

Write to one person

On a private blog, you know roughly who is reading. Write to that single reader in your head, with their context loaded. The result is more direct, less hedged, and more useful than anything aimed at "an audience."

Skip the throat-clearing

Public posts often open with context for strangers. Private posts can skip that. Your readers already know what you do and why; jump to the new information they came for.

Be specific about specifics

Use real numbers, real names, real screenshots. Private blogs are where you can finally stop generalizing. "We dropped p95 latency from 480ms to 210ms" beats "performance improved significantly" every time.

Show the work, not just the polish

Drafts, dead ends, and second-guessing are valuable for an inner circle. Public blogs reward polish; private blogs reward process. The two require different muscles.

Use the small format ruthlessly

A three-paragraph post is a complete unit on a private blog. You do not need to pad to 1,500 words to look serious. Length is a public-blog vanity metric; brevity is a private-blog kindness.

Invite replies

Private blogs work best as conversation starters. End with a real question, share the URL one-to-one, and treat the replies as part of the post. The medium is the loop, not the page.

The point of private writing

You write privately so you can think clearly. Engagement, in this medium, is not virality — it is the quality of the response from people who actually matter.

There is no shortage of places to put text on the internet. The right one depends on what you actually need. Below is a fair-minded comparison of Textpad.cloud against the categories of tools people most often weigh it against.

Vs. Pastebin-style tools

Pastebin clones are great for ephemeral text dumps. They fall apart the moment you want a real editor, image support, or a stable archive. Textpad is what pastebins would have become if they had ten more years of UX iteration.

Vs. Medium and Substack

Medium and Substack are publishing platforms with an audience layer. They are heavy on monetization and discovery, light on quick capture. Textpad is the opposite — it shines when you want a permanent URL fast, without a content strategy meeting.

Vs. Notion and Obsidian

Notion and Obsidian are knowledge bases. They reward structure: databases, links, tags. Textpad rewards flow: open, write, publish. For the long-tail notes that do not deserve a database row, Textpad is faster and the output is shareable.

Vs. Static site generators

SSGs (Hugo, Astro, Eleventy) give you maximum control and zero hosted cost — at the price of a build step, a repo, and a domain to babysit. Textpad gives you 95 percent of the result with none of the babysitting. If you measure cost in minutes of your life, Textpad wins.

Vs. Google Docs

Google Docs is a collaboration tool with a publishing afterthought. The URLs are ugly, the formatting is heavy, and nobody really reads a long-form doc inside Drive. Textpad is built for the reader; Docs is built for the editor.

Bottom line

Use the right tool for the right job. Textpad sits in the sweet spot between "a pastebin" and "a blog" — and that gap is wider than people assume.

After a few weeks of daily use, certain habits separate the people who love Textpad from the people who merely use it. Here are ten of them.

1. Bookmark a blank pad

Keep a new-pad URL in your bookmark bar. The fastest note is the one that starts before you remember you wanted to take it.

2. Learn the markdown shortcuts

Hash for headings, dash for lists, backticks for code. They are faster than the toolbar and they keep your hands on the keyboard.

3. Use the slash menu

Type / and pick the block. Slash menus are how Notion taught a generation to write — Textpad uses the same affordance without the rest of the Notion overhead.

4. Paste links liberally

Textpad unfurls links into rich previews. Pasting a URL is a real note, not a lazy shortcut.

5. Use one pad per topic, not per day

Date-based pads are a graveyard. Topic-based pads accumulate context that compounds over time.

6. Embrace public-by-default

If a note has no reason to be private, leave it public. Future-you searching Google for your own past thinking will thank you.

7. Use revisions instead of duplicating

When you rewrite, do it in place. Revision history keeps the old version. Duplicating pads fragments your archive.

8. Drop images from the clipboard

Screenshots, diagrams, photos — Cmd-V works for all of them. The asset is uploaded, hashed, and embedded; you keep writing.

9. Search before you write

Before starting a new pad, search your archive. You probably wrote down half of it already and just forgot.

10. Share the URL, not the screenshot

A URL stays current. A screenshot is dead the moment you take it. Always prefer the link.

Compound advantage

Each of these tips is small. Used together over a year, they turn Textpad from a notepad into a personal knowledge base that pays back every minute you put in.

Pointing your own domain at Textpad takes about ten minutes — most of which is waiting for DNS. This walkthrough covers everything from buying the domain to seeing your blog at example.com with a green padlock.

1. Pick the domain

Buy at the registrar you trust — Namecheap, Cloudflare, OVH, Porkbun, anywhere. The registrar does not matter, as long as you control the DNS records. Avoid TLDs that change pricing wildly between year one and year two.

2. Add the domain in Textpad

In your account settings, open the Domains tab and click Add domain. Type the domain you bought. Textpad will show you the DNS record it expects.

3. Add the DNS record at your registrar

For an apex domain (example.com), add an A record pointing at the IP Textpad gives you. For a subdomain (blog.example.com), add a CNAME record. Save and wait. DNS propagation usually takes a few minutes, sometimes longer.

4. Verify

Back in Textpad, click Verify. Once verification succeeds, Textpad issues an SSL certificate and your blog goes live on the domain — with HTTPS automatically. No manual cert handling.

5. Common gotchas

If verification keeps failing, check that you did not leave an old A record in place. Run dig or nslookup to confirm the record actually resolves to the value you typed. If the registrar offers "proxy" or "orange cloud" mode, leave it off during the first verification.

That is it

Your blog now lives at your own domain, with HTTPS, with all your existing posts intact. The /b/handle URL still works, so any external links you have already shared continue to resolve.

The web spent fifteen years convincing us that every action required an account. That assumption is finally cracking, and no-login publishing is back. Among the tools that get it right, Textpad.cloud stands out — here is why.

You write before you decide

Most thoughts die in the friction between idea and editor. Asking for a signup before the first sentence is the surest way to make sure that thought never gets written. Textpad inverts the order: you write first, then you decide whether to claim ownership.

The pad is yours from the start

Anonymous does not mean ephemeral. The URL is stable. The content is editable. The archive accumulates. When you eventually claim a handle, everything you wrote moves with you. No retroactive paywall, no "upgrade to keep your data".

It scales with your trust

You start anonymous. You add an email when you want backups. You add a handle when you want a public identity. You bring a domain when you want a brand. Each step adds capabilities without taking any away.

It is honest about the tradeoffs

No-login means anyone with the URL can read your pad. That is the deal. Textpad does not pretend otherwise — and it gives you per-pad visibility controls when you need stricter privacy.

The bottom line

Friction kills creative output. Textpad removes the upfront friction without removing the long-term capabilities. For publishing-without-the-tax, it is the cleanest answer on the modern web.