Put your Twine story online so readers can open it from a link. Publish the story to an HTML file, drop it above and get an HTTPS address in seconds. No terminal or account is needed to try it, and keeping the story in a free account removes the initial expiry.
How it works
- Publish the story to a file. In Twine, use Publish to File to create the playable HTML. This is the story readers open, rather than a Twee source file or an editor backup.
- Drop the HTML above. For a story with external images or audio, collect the HTML as
index.htmlwith its media in a folder and upload the whole folder or ZIP. The first link lasts 6 hours. - Keep your story's link. Choose Keep it free → to move it into a free account. Publish later revisions to that same site so readers don't need a new address.
One story file, or a folder with media
A text-only Twine story can be one HTML file. Lobsite makes a single uploaded HTML file open at the site's root address. For a media-rich story, give it a folder like this:
story/
index.html
images/
hallway.webp
audio/
rain.ogg
Reference the image as images/hallway.webp, with the exact spelling and case. A path on your own computer won't work for a reader. If files live on another host, use HTTPS URLs. See Twine's publishing guide for its HTML publishing workflow.
Story formats and reader saves
Lobsite serves the HTML that Twine generates, including the story format's scripts and your styles. It doesn't convert passages or change the story's format. Test the finished story with the format and browsers your readers use.
Where a story format uses browser storage for progress, saves belong to that browser and origin. A preview URL or a move to a custom domain can have a separate set of saves. Keeping the same live address helps returning readers, but a story revision can still affect old saves depending on its format and your changes.
Share a draft with readers
For a separate test version, put the story in a folder and deploy it with npx lobsite ./story --preview after claiming the site. Your live story stays as it is while readers check the new draft. On Standard, a site password protects both live and preview addresses.
Free allows 5 MB per file, 50 MB total, 100 files and 10 GB of bandwidth a month. Embedded audio can make a single HTML file surprisingly large. The drop box accepts up to 25 MB per upload; the HTML5 hosting guide explains larger uploads and Standard's limits. Free also adds a small badge to the bottom-right corner of the page.
A deploy without an account is live for 6 hours. The claim link keeps it, free.
Preview before going live. Roll back in one click, redirects and all.
Files are stored by their hash. Redeploying an unchanged site uploads 0 bytes.
Every site gets a *.lobsite.app address with HTTPS from the first deploy.
Free accounts included: add one DNS record and the site moves to your domain. Every site has HTTPS on any plan.
Redirects, headers and forms live in lobsite.toml and travel with each deploy.
Ways to share a Twine story
| Method | Reader experience | When it helps |
|---|---|---|
| A Lobsite story URL | Open a link and start reading | Publishing and updating a story online |
| An HTML download | Download and open the story file | Distributing an offline copy with suitable assets |
| A Twee source file | Import or compile it with authoring tools | Sharing editable source with another author |
For other single-file projects, see HTML file hosting. For games made in an engine, start with HTML5 game hosting.
Frequently asked questions
Do I need to write code to host a Twine story?
No. Use Publish to File in Twine and drop the resulting HTML above. If the story uses separate media files, upload them together in a folder.
Can I publish a .twee file directly on Lobsite?
It can be stored as a file, but it won't become a playable story. Compile or publish it to HTML with the appropriate authoring tools first.
Why are the images missing from my published Twine story?
Check that you uploaded the media with the HTML, that paths are relative to the story and that file names match exactly. Paths to files on your computer won't work online.
Will updating my Twine story preserve every reader's save?
That depends on the story format and your changes. Keeping the same origin avoids moving readers to separate browser storage, but test existing saves before publishing a major revision.