Back to Help Center
Build StacksApril 7, 2026

How to Change the Stack Mid-Build

You're not locked into a stack once you start building. Trovn lets you change the Build Stack at any time during the build process.

How to Switch Stacks

  1. Open the Builder — Navigate to the AI Builder where your current build is in progress.
  2. Find the Stack Selector — Look at the builder header bar. You'll see the current stack displayed (e.g., "HTML/Tailwind" or "Restaurant").
  3. Click the Stack Selector — A dropdown will appear showing all available stacks.
  4. Choose Your New Stack — Select the stack you want to switch to.
  5. Send a New Prompt — After selecting the new stack, type or modify your build prompt and send it. The AI will rebuild the site using the new stack's approach.

What Happens When You Switch

  • The AI rebuilds from your prompt — It takes your current prompt and generates fresh output using the new stack's code structure, design patterns, and features.
  • Your previous versions are safe — Every build is saved in your build history. Switching stacks doesn't delete or overwrite anything. You can always go back to a previous version.
  • The design will change — Different stacks produce different layouts, code structures, and included sections. Expect the output to look and feel different.

When to Consider Switching

  • The output doesn't match the project type — If you started with a generic stack but realize an industry stack would be better, switch.
  • You want to try a different code approach — Want to see how the same site looks as Next.js vs. HTML/Tailwind? Switch and compare.
  • The client changed requirements — If the project scope changed (e.g., from a brochure site to a landing page), switch to the stack that fits the new goal.
  • You want to experiment — Build history keeps everything, so there's no risk in trying different stacks to see which gives the best result.

Tips

  • Be specific in your prompt after switching — The more detail you give the AI about what you want, the better the output regardless of stack.
  • Compare versions — Use build history to compare outputs from different stacks side by side.
  • Don't switch stacks to fix small issues — If you like the overall output but want to tweak details, iterate with follow-up prompts on the same stack instead of switching.