Native Windows editor / R0 release

Write one controlled template.

Inspect what it means. Generate distinct variants locally.

  • Windows x64
  • Works offline
  • No account required

A readable authoring loop

Everything stays visible.

Template, rendered result and diagnostics share one focused workspace.

Spintax Studio
Spintax Studio showing a template editor beside its rendered page preview
Template, live preview and source diagnostics in one window.

The product

Every decision stays visible.

Spintax Studio is built around the moment an author changes a template and needs to know what happened next.

01

Write with the language

Bracket matching, syntax colours and a fixed-pitch editor keep alternatives, variables, conditions and directives easy to scan.

02

See the result immediately

The preview is rendered by the same engine used across the Spintax family. What you see is not a second parser's approximation.

03

Fix the cause, not the symptom

Diagnostics point to the source position, explain the rule and connect to built-in help with measured examples.

04

Generate and export locally

Inspect variables and includes, edit groups, generate seeded variants and export the result without a runtime or network service.

The workflow

From source to a checked result.

  1. 01
    Author

    Compose the choices and rules that define your content.

  2. 02
    Validate

    Follow a diagnostic to the exact bracket, directive or definition.

  3. 03
    Preview

    Read the rendered page or inspect the generated source.

  4. 04
    Export

    Generate deterministic variants and take the files where they belong.

R0 release

Local by design.

Spintax Studio does not require an account, a model key or a connection. Documents stay on your computer and the editor does not include generative AI in this release.

Read the full privacy policy

One language family

Built on a shared engine.

The editor consumes the open-source Spintax engine used by the JavaScript, PHP and Python implementations. One corpus keeps the language behaviour aligned across deployments.

See the engine on GitHub