Move your team from NovelAI to Sudowrite.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Sudowrite — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in NovelAI is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Both tools generate new prose from the current cursor position or selection, acting as a co-author. Moving from NovelAI to Sudowrite: export your story text from NovelAI (copy from the web editor or use the download option), paste it into a new Sudowrite project's Draft section, then use the Write tool (Auto mode for open-ended continuation, Guided mode when you have a specific direction). Moving from Sudowrite to NovelAI: copy your draft text into NovelAI's web editor and place the cursor where you want the AI to continue. NovelAI offers generation controls (temperature, top-p, top-k) directly in its editor; in Sudowrite, use the Creativity slider in Draft or the Guided mode direction prompt to steer output. Neither product offers a direct export API, so migration is copy-paste.
- Warning: NovelAI's generation settings (temperature, sampler type, repetition penalty) have no direct equivalent in Sudowrite's Write tool — Sudowrite abstracts these into Prose Mode selection and a Guided mode prompt.
- Warning: Sudowrite's Write tool consumes credits per generation; NovelAI's text generation is unlimited on all paid tiers with no credit drain, so heavy users may hit Sudowrite plan limits faster.
- Warning: NovelAI supports a Text Adventure Mode for interactive narrative formats; Sudowrite has no equivalent — structured story work is done through Scenes and Draft instead.
Both tools provide a persistent knowledge store that the AI references while generating prose. NovelAI's Lorebook uses keyword-triggered injection: entries activate automatically when their trigger words appear in the story context. Sudowrite's Story Bible is a structured set of sections (Characters, Worldbuilding, Genre, Style, Synopsis, Outline) that inform all generation globally rather than by keyword. Moving from NovelAI to Sudowrite: for each Lorebook entry, copy the entry text into the appropriate Story Bible section (character entries → Characters, location entries → Worldbuilding, faction/lore entries → Worldbuilding). You will lose keyword-trigger precision — all Story Bible content is always in context. Moving from Sudowrite to NovelAI: split each Story Bible section into discrete Lorebook entries, assign relevant trigger keywords (character names, location names, faction names), and set Always-On for entries that must always be present. Use NovelAI's Lore Generator to auto-draft entries from names if starting fresh.
- Warning: NovelAI's Lorebook supports regex-based keyword triggers, AND logic, random-chance activation, and numeric conditions; Sudowrite's Story Bible has no conditional injection — all content is applied globally on every generation.
- Warning: NovelAI's Lorebook entries have token budgets and placement controls (insertion position, trim direction); Sudowrite's Story Bible does not expose token-level context management.
- Warning: Story Bible sections in Sudowrite can be AI-generated from a Braindump or Synopsis, streamlining initial setup; NovelAI's Lore Generator drafts individual entries but there is no bulk-generate-from-synopsis workflow.
Both platforms help writers improve or expand existing prose, but through different interaction models. NovelAI's refinement relies on Writers Toolbox composition aids and re-generation with adjusted module/sampling settings to change tone, style, or detail level. Sudowrite offers three dedicated inline tools: Rewrite (rephrase or improve selected text), Describe (add sensory detail to a passage), and Brainstorm (generate creative lists for names, plot elements, worldbuilding). Moving from NovelAI to Sudowrite: instead of re-running generation with different settings, highlight the passage in Sudowrite's editor and use Rewrite for tone/phrasing changes or Describe to add sensory richness; use Brainstorm to generate the kind of creative lists you might have produced by iterating prompts in NovelAI. Moving from Sudowrite to NovelAI: paste the passage to refine into the NovelAI editor, use the Writers Toolbox, and adjust Module/sampling settings then re-generate from just before the passage to produce an alternative version.
- Warning: Sudowrite's Rewrite, Describe, and Brainstorm tools each produce multiple option cards to choose from; NovelAI does not offer a native multi-option selection UI — you must re-generate or use retry to get alternatives.
- Warning: NovelAI's Chat Format mode for dialogue-heavy writing has no direct equivalent in Sudowrite's refinement tools; Sudowrite users would instead use Write (Guided mode) or a custom Plugin for dialogue work.
- Warning: Sudowrite's Describe tool generates five sensory dimensions (sight, sound, smell, touch, taste); this level of structured sensory generation is not built into NovelAI's toolbox and must be approximated by manual prompt engineering.
Both platforms can generate full chapters, but the workflow structure differs significantly. NovelAI generates prose linearly — the writer maintains a running document and the AI continues from the cursor position; chapter structure is entirely managed by the writer in the editor. Sudowrite's Scenes and Draft workflow formalises structure: the writer creates scene-level beat summaries (each covering one location, timeframe, or character context), then the Draft tool generates full prose for the entire chapter from those beats, informed by the Story Bible. Moving from NovelAI to Sudowrite: review your outline or plan and break each intended chapter into scene beats (aim for 3-6 scenes per chapter); enter these in Sudowrite's Scenes section, then click Generate in the Draft tool. You can add a single Extra Instructions note for chapter-level tone or plot direction. Moving from Sudowrite to NovelAI: take each generated scene's prose and paste it as a running document in NovelAI, then continue generating from the end of the last scene — NovelAI will pick up the narrative continuity.
- Warning: Sudowrite's Draft tool applies one Extra Instructions field to the whole chapter, not per scene; NovelAI lets you write any amount of inline direction between passages with full cursor-placement control.
- Warning: Sudowrite chapter length scales directly with scene count — adding more scenes produces longer chapters; NovelAI chapter length is determined solely by how long you let the AI run and how many times you continue generation.
- Warning: Sudowrite's Draft tool uses Story Bible (Characters, Worldbuilding, Genre, Style) as automatic context; NovelAI requires that equivalent context live in the Lorebook with correctly configured keywords or token budgets.
Both tools let writers steer the AI's prose style and model behavior, but the mechanisms differ. NovelAI uses Modules (fine-tuned style overlays applied on top of the base model) plus granular sampling sliders (temperature, top-p, top-k, repetition penalty). Sudowrite replaces that with Prose Modes: Muse (proprietary fiction model), Excellent (Claude 3.7 Sonnet), and Basic (GPT-4o Mini), plus access to a broad experimental model roster (GPT-4.1, Gemini 2.5, DeepSeek, etc.). Moving from NovelAI to Sudowrite: identify which NovelAI module you relied on (e.g., a Literary style module) and pick the Sudowrite Prose Mode that best matches — Muse for fiction-first, Excellent for complex instruction-following. Set Style Examples in Sudowrite (up to 1,000 words of your prose) to anchor the model to your voice. Moving from Sudowrite to NovelAI: pick the appropriate base model (Erato for high-quality text), then select the Module closest to your Prose Mode preference, and tune temperature/top-p to match your target output style.
- Warning: NovelAI's Modules are tied to the selected base model — not all modules are available on every model; Sudowrite's Prose Modes and experimental model list apply across all tools without per-feature gating.
- Warning: Sudowrite exposes no manual sampling parameter sliders (temperature, top-p); NovelAI exposes these directly, so writers who tune parameters precisely will lose that control when switching to Sudowrite.
- Warning: Sudowrite's experimental models (GPT-4.1, Gemini 2.5, Grok 4) consume credits at higher rates than Muse — switching models can burn through a plan's credit allowance significantly faster.