TSUMIMI TIME Demo: What the Free Build Includes

The demo is not a slice of the main game. It is a separate Steam application with its own AppID, released four months before the full version, and nothing you do inside it carries over. That single fact answers most of the questions people search for, and it is the reason this section exists instead of a single line on the release page.

Source note: AppID, release date and store text are taken from Steam's public API. Behaviour inside the demo (what the build contains, how far it goes) comes from our own playthrough. Claims we could not reproduce are marked Unverified rather than stated as fact.

The three demo pages, in the order people need them

Read them in this order if you have not installed it yet, and jump straight to the third if you already own the game and are only here about a lost save.

The order is deliberate. The scope question comes first because it decides whether you install at all; the gameplay question only matters after you have; and the language question is the one that sends people looking for a bug report that is really a translation gap.

What the demo actually is

A standalone build. Not a chapter-one trial, not a time-limited unlock, not a shared executable with a paywall.

Because it is a different app, owning the demo does not mark the full game as owned, and uninstalling one does not touch the other. It also means the achievement rates on the main app are unaffected by demo players — the demo has its own statistics page.

The three questions people actually ask

"Does my demo save carry over?" No. This is the single most common point of confusion, and it is not a bug. The two builds use separate save locations, and there is no import path. The demo save page walks through where each build stores its data and why copying files does not work.

"Why does the demo feel different from the full game?" Because 1.0.1 changed the economy. The demo build predates the patch that raised starting funds, so the early game is noticeably tighter there than in the release version. If you bounced off the demo's money pressure, that specific complaint was addressed.

"Is English supported in the demo?" Yes, the interface has an English option, but the coverage is not identical to the retail build's. The demo English page goes through what is translated and what stays in Japanese.

What the demo lets you judge, and what it hides

This is the part a "free trial" page normally skips. A demo can only answer questions the build actually exposes.

The honest summary: the demo is good at telling you whether you can look at this interface for fifteen in-game days. It is bad at telling you whether the story pays off, because it stops well before the payoff.

How the demo compares to the full release

If you are deciding between the two, the price page covers what the paid version costs by region, and the gameplay page covers the loop the demo only partially shows.

What the demo cannot tell you about endings

The demo stops before the deduction becomes the deciding mechanic, which means it cannot demonstrate the one thing this game is built around. Nobody finishes the demo holding an opinion about whether nine endings is too many or too few, because the demo never asks.

That is worth knowing before you read demo impressions as reviews. A common pattern in the first week: someone plays the free build, enjoys the interface, buys the full game, and then finds that the interface was never the hard part — the search and the money were. The gameplay page is the honest preview of that half, and the endings hub is what the paid version adds on top.

The questions the demo leaves open, and where they are answered

Two more pages are useful if the demo left you with a mechanical question rather than a story one: the walkthrough for the day structure, and the troubleshooting index for anything that behaved unexpectedly. If the demo crashed or a keyword refused to register, the same symptom pages apply — the builds are close enough that the fixes are identical.

Should you play the demo first?

For most people, yes — it costs nothing and the download is small. Two exceptions.

If you already know you will buy it, skip the demo. Its economy is out of date, so the money squeeze you experience is not the one you will actually face, and starting fresh in the retail build is less confusing than unlearning a tighter loop.

If your machine is borderline, the demo is the cheapest possible compatibility test. If it runs, the full game will: they share an engine and roughly the same requirement tier.

Either way, do not treat the demo as a review substitute. The story section is where the payoff lives, and the demo does not reach it.

Quick index

The pages below are the ones that come up while deciding whether the free build is enough.

• All nine endings — what the paid version adds
• How the loop actually plays — the half the demo hides
• Achievement rates — how many players reach each branch
• Gift timing calculator — the deadline system the demo barely touches
• Story overview — where the payoff lives, without spoiling the ending
• Troubleshooting index — applies to both builds
• Open questions — including what the demo does not settle
• Community section — what buyers said after the demo
• Full guide index — if the demo convinced you and you want the loop map first
• Regional edition differences — matters if you are buying outside the US
• Keyword not registering — the demo shows this bug's symptom clearly

Where the demo stops

It ends before the branch structure becomes visible, which means it cannot show you the thing the game is actually built around — the deduction that decides which of the nine endings you get. That is not a criticism; it is what a demo is for. Just do not read a demo impression as a verdict on the ending system.

If what you want is a sense of how the deduction works before spending anything, the walkthrough describes the loop without giving away answers, and the open questions page lists what we still cannot confirm about it.