💡 Frequently Asked Questions

TweePorter.ca is a web-based compiler that converts interactive stories written in Twee format into pure HTML/CSS files. These files can be embedded on any website platform, including those that block JavaScript like WordPress, Wix, and Squarespace.

While Twine creates interactive stories that require JavaScript to run, TweePorter compiles stories into pure HTML/CSS that works everywhere—even on restrictive platforms like WordPress.com, Wix, and Squarespace that block JavaScript. TweePorter is specifically designed for website embedding, while Twine is better for standalone story files.

No! TweePorter uses simple Twee syntax that's easy to learn. You can write stories using basic formatting like **bold** and [[links]]. We also provide AI-assisted prompt templates and a visual story planner to help you get started.

Twee is a simple text format for writing interactive stories. It uses :: PassageName to create story sections and [[Link Text|Destination]] to create clickable links between passages. TweePorter supports SugarCube-style Twee syntax.

Simple 4-step process:

• Step 1: Write your story in Twee format (or use our AI prompt helper)
• Step 2: Customize colors and layout options
• Step 3: Click "Compile Story" to generate HTML
• Step 4: Choose your export format and embed on your website

Yes! We provide an AI Suggested Prompt template specifically designed for generating Twee stories with ChatGPT, Claude, or other AI assistants. The prompt helps AI understand SugarCube syntax and create properly formatted interactive stories.

TweePorter works on virtually any platform that accepts HTML, including:

• WordPress (WordPress.com and self-hosted)
• Wix
• Squarespace
• Shopify
• Webflow
• Notion (with embed blocks)
• Ghost
• Any static HTML website

For WordPress, use the "WordPress Custom HTML Block" export format:

• Compile your story in TweePorter
• Click "WordPress Custom HTML Block" to download
• In WordPress, add a "Custom HTML" block
• Open the downloaded file and copy the entire content
• Paste into the Custom HTML block
• Save and publish!

For Wix, use the "Universal Raw HTML Snippet" or "Responsive iFrame Template":

• Compile and download your story
• Upload the HTML file to Wix's Media Manager
• Add an "Embed Code" element to your page
• Use an iframe pointing to the uploaded file URL

Yes! Squarespace supports HTML embedding through Code Blocks. Use the "Universal Raw HTML Snippet" export, then add a Code Block to your Squarespace page and paste the content.

Many website platforms (especially WordPress.com, Wix, and Squarespace) block JavaScript for security reasons. Twine stories rely heavily on JavaScript to function. TweePorter solves this by compiling stories into pure HTML/CSS that doesn't require JavaScript.

TweePorter offers 8 different export formats:

• Full HTML Page - Standalone story file
• WordPress Custom HTML Block - Direct paste into WordPress
• WordPress CMS Pack (ZIP) - Separate HTML/CSS files with README
• Universal Raw HTML Snippet - Generic CMS-compatible code
• Standalone HTML + CSS Files - Separate files for flexibility
• Minified Single-File HTML - Compressed version for faster loading
• Responsive iFrame Template - Embed code with instructions
• Email-Safe Static Preview - First passage only for email campaigns

TweePorter supports multiple layout styles:

• Classic/Standard - Traditional centered story text with links below
• Left/Right Columns - Story text in center (60%) with navigational links in side columns (20% each)
• Mind Map - Visual breadcrumb navigation showing story path

Yes! You can customize:

• Text colors (bold, italic, headings)
• Link colors and hover effects
• Background colors for text and frame
• Layout type (Classic, Left/Right, Mind Map)
• Typography and formatting styles

TweePorter supports SugarCube syntax:

• Passages: :: PassageName
• Links (pipe): [[Display Text|Destination]]
• Links (arrow): [[Display Text->Destination]]
• Simple links: [[Destination]]
• Bold: **text**
• Italic: *text* or _text_
• Headings: !Title or # Title
• Strikethrough: ~~text~~

We also maintain backward compatibility with Twine 1 arrow syntax.

TweePorter itself has no file size limits. However, your target platform may have upload restrictions (WordPress typically limits file uploads to 2-10MB depending on your hosting). The minified export option can help reduce file sizes by up to 30%.

Your story is saved in your browser's local storage, so you can close the tab and come back later. However, we recommend downloading your Twee source code regularly as a backup. Clearing browser data will erase local saves.

TweePorter is currently completely free with no account required. All features including the compiler, visual editor, and all export formats are available at no cost.

No account is required! You can use TweePorter immediately without signing up. All features work directly in your browser.

Yes! You can use TweePorter to create interactive stories for any purpose, including commercial websites, educational content, marketing campaigns, and business presentations.

Currently, there are no limits on the number of stories you can create or compile. You can generate as many exports as you need.

TweePorter includes two visual tools:

• Visual Story Planner: AI-powered chapter planning with branching story structure visualization
• Visual Editor (Beta): Node-based graph editor for creating and editing story passages

Both tools export to Twee format compatible with the compiler.

This usually means the HTML wasn't pasted correctly. Make sure you:

• Used the correct export format for your platform (WordPress Custom HTML Block for WordPress, etc.)
• Copied the entire content from the downloaded file
• Pasted into a Custom HTML or Code Block (not a regular text block)
• Didn't modify the code after pasting

CSS conflicts with your website theme can cause styling issues. Try:

• Use the WordPress Custom HTML Block format which has scoped CSS
• Use the iFrame Template to completely isolate the story from your site's styles
• Contact us with a screenshot and we can help troubleshoot specific issues

Common compilation issues:

• Make sure you have at least one passage starting with :: Start
• Check that all link destinations match actual passage names (case-sensitive)
• Verify link syntax: [[Text|Passage]] not [[Text | Passage]] (no spaces around pipe)
• Make sure passage names don't contain special characters like | or ]]

The Left/Right layout automatically splits unmarked links (first half left, second half right). For manual control, add markers:

• [[Link Text {{{left}}}|Destination]] - Forces link to left column
• [[Link Text {{{right}}}|Destination]] - Forces link to right column

All TweePorter exports are mobile-responsive by default. If you're experiencing issues, make sure your website platform isn't adding conflicting mobile styles. The iFrame Template export works best for mobile compatibility.

We're here to help! You can:

• Check our example stories on the homepage for inspiration
• Review the Quick Guide in the compiler for syntax reference
• Contact us through the website with specific questions

Yes! If your Twine story uses SugarCube format, you can export it as a .twee file from Twine, then paste the code into TweePorter. Note that advanced JavaScript features from Twine won't work in TweePorter's HTML/CSS output.

Currently, TweePorter focuses on text-based interactive fiction. Image support is planned for a future update. For now, you can include image URLs in your story text as regular links.

Simply create passages for each branch and ending:

• Create a passage for each decision point
• Add links to different paths based on choices
• Create separate ending passages with no outgoing links
• Use descriptive passage names to keep track of story branches

The Visual Story Planner is perfect for planning complex branching narratives.

Currently, TweePorter creates stateless interactive stories without save functionality. Each time a reader refreshes the page, they start from the beginning. This is a limitation of the pure HTML/CSS approach needed for platform compatibility.

• Use the live preview in TweePorter to test all story paths
• Download the Full HTML Page and open it locally in your browser
• Check all links to ensure they lead to correct destinations
• Test on mobile devices to verify responsive design
• Have someone else play through your story to find issues you might miss

Yes, but it's best to use the iFrame Template export for each story to prevent CSS conflicts. The WordPress Custom HTML Block format also has scoped styles that should work for multiple stories on one page.