Host a guide and share it as a link
Put documentation, a manual or a how-to online at its own address — so it can be bookmarked, linked from support replies, and corrected without re-sending.
Drop your guide here
Any other file works too — up to 25.0 MB, or 100.0 MB for a whole site
Free to use, live at your-name.99helpers.site in about ten seconds.
Why this is harder than it should be
A guide is written once and referred to for years, which makes it exactly the wrong thing to distribute as an attachment. It needs an address people can bookmark, support can paste into a reply, and you can correct the moment someone points out that step four is wrong.
Attachments can't be bookmarked
Nobody keeps a PDF in a place they can find again. They ask you for it a second time, which is a support cost you're paying repeatedly.
Support pastes stale copies
If the guide lives as a file, whichever copy an agent has is what the customer receives — including the version from before the interface changed.
A full documentation platform is too much
For one manual or a handful of how-tos, a docs platform with its own build pipeline and hosting bill is a great deal of machinery.
How it works
- 1
Decide between a page and a document
An HTML guide is searchable in the browser, linkable by section, and reads well on a phone. A PDF preserves layout and prints properly. Both work — pick by how it'll be used.
- 2
Give it a permanent address
setup-guide, api-docs, staff-handbook — short, obvious names people can type from memory and support can paste without looking up.
- 3
Publish, then correct freely
Every fix reaches everyone immediately, because they're all reading the same address rather than their own copies.
Worth knowing
- An HTML guide can have anchor links to sections, so support can send someone directly to the relevant step.
- A multi-page guide works as a folder — internal links between pages resolve normally.
- Add a 404.html so a mistyped section link lands somewhere useful rather than on a bare error.
- Markdown is served as plain text; convert it to HTML if you want a formatted page.
- Guides containing internal procedures or credentials shouldn't be public.
Questions
- HTML or PDF for a guide?
- HTML if people will read it on screen — it's searchable, linkable by section and reads properly on a phone. PDF if the layout matters or people will print it. Hosting both is common.
- Can I host multi-page documentation?
- Yes. Upload the folder and the links between pages work as they do locally, with clean URLs — /getting-started serves getting-started.html.
- Can I link someone to a specific section?
- In an HTML guide, yes — standard anchor links work, so support can send a customer straight to the relevant step.
- How do I correct a mistake?
- Publish the corrected version to the same address. Everyone reading the guide sees the fix immediately, including anyone who bookmarked it months ago.
Try it with what you have right now
Drop it in at the top of this page and see the link for yourself. You only make an account once it's ready to go live.
Hosting guides by file type
Other things people host
Everything gets its own address on 99helpers.site — see everything you can host or free file hosting for any file type.