You don’t need Python
to write a visual novel.

You already know how to write and draw. There’s no reason to become a programmer along the way.

One day we got tired of this

  • Tired of learning Python just to write a story.
  • Tired of a stray space breaking everything.
  • Tired of downloading a monstrous Android SDK and Java Development Kit just to put the thing on a phone.
  • Tired of a visual novel taking longer to load than 3D shooters and strategy games.
  • Tired of programs saying “your computer is too old”.

Enough!

None of these problems are inevitable.

How we do it

  1. You write it like a play.

    There is no separate “code”: the engine reads a screenplay as a screenplay, with ordinary Markdown markup. If you already know how to make text **bold** or *italic*, you know about half the language.

  2. You put the pictures next to it.

    Backgrounds and sprites are ordinary image files, sitting next to the text.

  3. You open it.

    The story, the pictures, and a small program that plays them. You don’t have to “build the project.”

This is what it looks like

hamlet.vnrs
# Scene 1

![](bg/elsinore_night.png)

> Elsinore. A platform before the castle.

Barnardo::
Who's there?

Francisco::
Nay, answer me. Stand and unfold yourself.

::
Enter Ghost.

Horatio::
Stay! speak! I charge thee, speak!

+ [Speak to it](speak.vnrs)
- [Let it pass](silence.vnrs)

A slice of Hamlet, Act I, Scene 1. The engine reads the file as-is.

What we’re aiming for

  • A program you can download, unpack, and run, without extra installs or setup.
  • A story in markup you can actually read — a beta reader, an editor, or you in six months.
  • An engine that stays separate from the screenplay, so you can write on a phone and play on a computer, in a browser, or as a book, without rebuilding.
  • Machines from the last century, not only new ones.
  • Rollback, line history, a gallery and a choice diagram included, without extra plugins.
  • Look settings the reader can change, for every VN.
  • Saves and screenplays that don’t break after an engine update. Ever.
  • No coder on the team. At all.

Where we are

Vinora is still being built, and as of 29 August 2026 this site is a manifesto more than a product page. On Linux you can already open a scene and watch the dialogue go — in Russian, Japanese, or whatever else you throw at it. How to write choices, sprites and music is already figured out; the engine is still catching up.

The beta is planned for the first quarter of 2027.