Why this site exists
Information about The Freak Circus is spread across playable builds, development notes, and community conversation. This site brings the questions players actually ask into one readable place: who the characters are, what the current build contains, where Day 3 stands, and how to play on a suitable platform.
Organising that information is not the hard part. The hard part is staying restrained while the information is still incomplete. The game is mid-development: of five introduced characters, only two have planned routes; of four announced endings, one is implemented; Day 3 is still being made and has no date. Under those conditions it is easy to find guides that look complete while being substantially guesswork.
That is why this site treats "how far can we confirm" as the more important question than "how much can we write". An honest answer and a confident-sounding guess are worth very different amounts to a reader, and only one of them can be acted on.
How facts, plans, and speculation are handled
Material reproducible in a public build is described as current content. Developer intentions that have not shipped are labelled as planned or in development. Community theories, unsupported route names, and claims that cannot be reproduced in play are not rewritten as facts.
In practice that shows up as follows. Character pages state the official height and age order, and separately flag which appearance and relationship details come from the fandom wiki rather than from the developer. The endings page states that exactly one ending is playable and lists the four planned ones separately, rather than implying that multiple endings can be reached today.
What we decline to repeat matters just as much. The following circulate across fan sites as settled fact, but none of them have a first-party source, so this site does not present them as conclusions:
- The game supports a specific number of save slots, autosaves at fixed intervals, or stores saves in a named folder. โ No official save documentation exists. Ren'Py builds use a standard location, but the developer has not published specifics.
- Browser saves can be exported to a zip archive and imported into a desktop build. โ Ren'Py offers an export and import action in its engine overlay, but the developer has not confirmed a browser-to-desktop workflow for this game.
- The full game takes a specific number of hours to complete. โ Only an average session of about half an hour is published. A total completion time has never been given.
- Day 3 has a confirmed release month. โ No date has been announced. The developer has explicitly asked that outside date claims not be repeated.
- The game contains a specific total number of endings. โ The developer has said multiple endings are planned but cannot give a number.
- Each character has a stated exact age, birthday, or a published age list in numerals. โ Only a relative age order and a height chart were published. Birthdays and numeric ages circulating online are not first-party.
Why there is no full walkthrough
This is the point most often misread about this site, so it is worth stating plainly. Right now the game has one implemented ending, and the scripts for both romance routes are still being written. Where there is no trigger, there is no honest trigger chart.
Guides that specify picking a red balloon or avoiding defiance on Day 2 are describing a public build that does not exist. A reader who follows them finds no route at all, which is more confusing than having no guide in the first place. This site will add the real choices, scenes, and save points once the routes actually ship.
Where our information comes from
Primary sources are the developer's itch.io page and devlog, and the official Tumblr FAQ and AMA posts. The height chart and age order quoted on the character pages come from images and answers published by the developer directly, not from sprite estimates or fan compilations.
- Official itch.io game page โ
- Official itch.io devlog โ
- Official Tumblr FAQ โ
- Official Tumblr Askbox FAQ โ
- Official Tumblr AMA โ most popular questions โ
- Official Tumblr AMA โ answers part 5 โ
Every page that cites a specific fact links the source it came from, so you can check it independently rather than taking our word for it.
This site is not official
This is not the developer, publisher, or an official support channel, and it does not present itself as one. Explanations and organization are independent editorial work; the game, characters, artwork, and related marks remain the property of their respective rights holders.
The developer has stated that the itch.io page is the only official page for the game and has asked that it not be re-uploaded or reposted, and has confirmed that no official Discord server exists โ so any server or account not linked from the official pages should be treated as fan-run or unauthorized.
This site does not host game files and does not mirror the download packages. The optional player on the site is served by a third-party host, which the privacy policy covers.
Media, community work, and rights
The site does not repackage or host game files, and it does not turn fan work found online into an unlicensed house gallery. Community selections are curated by hand, remain the work of their creators, and are withheld when source, permission, or attribution is unclear.
Some appearance and relationship detail on the character profiles comes from the fandom wiki. That material is labelled as fan-derived on the page and kept visually separate from developer-confirmed facts, so a reader can decide how much weight to give it.
How version-sensitive information is maintained
Version-sensitive information is maintained through the on-site Updates and Day 3 pages. Character profiles state where the evidence ends instead of inventing endings simply to make a page look complete.
The game is still a prototype, and its script, labels, and save behaviour can change between builds. If a page here conflicts with the current build, please say so.
Corrections and updates
If a page conflicts with the current build, lacks important context, or needs an attribution correction, use the Contact page and identify the affected page and specific issue. Reproducible, well-located reports are reviewed first.
Additions are welcome too. If there is a question you want answered here and no page covers it yet, tell us.