Which 2026 Interactive Fiction Event Fits Your Visual Novel Now?

September 17, 2026

Which 2026 Interactive Fiction Event Fits Your Visual Novel Now?

A visual novel creator can find several interactive fiction events in the same search and still choose the wrong one. One event wants a finished work that can stay discoverable for the year. Another is built around an opening that needs feedback. A third freezes entries for public judging and a final ranking. Sending the same build to all three without reading the rules misses what each audience has agreed to do.

The 2026 calendar makes that difference visible. IntroComp announced its results on September 12 after evaluating eight openings. IFComp closed author submissions on August 28 and is now in its public judging period. The Interactive Fiction Showcase remains open through the end of 2026 for completed works. These are not three sizes of the same promotion. They are three different promises between a creator, an organizer, and players.

Start with the state of the work, then choose the kind of attention you need. Only after that should you prepare a page, package, or public link.

Is the work an opening, a judged release, or a finished catalogue entry?

The first distinction is completion.

IntroComp exists for excerpts of interactive fiction. Its purpose is to let an author present an opening, learn from audience reactions, and use that feedback to finish the larger work. The 2026 submission window is already closed, so it is not an immediate destination in September. It is still a useful model for planning: an opening can be public on purpose when the event has explicitly promised feedback on unfinished work.

IFComp asks for a competition entry by a fixed deadline. Its public judges play entries and score them from one to ten, with the final ranking based on average ratings. The 2026 games entered public judging on September 1, voting closes October 19, and the awards ceremony is scheduled for October 24. A creator who missed the August deadline should watch and learn this year rather than treat the live ballot as a late submission form.

The Interactive Fiction Showcase uses a different structure. It is an unranked, year-long itch.io event for interactive fiction completed in 2026. Its rules explicitly include visual novels, accept works in any language, and allow more than one entry. On September 17, the live page showed 175 entries and 255 joined participants. That number shows an active catalogue, not a guaranteed audience for every work.

A creator compares a rough opening with an assembled complete story stage

The showcase also requires a playable, complete work at the time of submission. A previously public demo does not disqualify a game that was completed in 2026, and a work may have appeared in another event. The important boundary is that the submitted version is now complete. A strong first chapter with three unwritten routes is still an opening, even if it looks polished.

Write one sentence before choosing an event: “This version is public because I need...” Finish it with one outcome. If the answer is structural feedback on an opening, seek a feedback format. If it is concentrated scoring and comparison, prepare for a future ranked competition and its deadline. If it is a durable place for a complete 2026 release to be found, the year-long showcase may fit.

Read the asset rule before planning promotion

Completion is not the only gate. The current Interactive Fiction Showcase rules say submitted assets must be properly credited and that entries should contain no generated AI content, including the title card and game page. The rule describes the submitted content, not the name of the authoring tool.

That distinction matters for Novelez users. Building scenes in a no-code editor does not by itself tell an organizer where the writing, character art, backgrounds, music, or cover came from. Conversely, replacing only the game script while leaving a generated cover or page image can still conflict with a rule that includes promotional material.

A creator traces every visual and audio asset to its source before entry

Audit the actual entry asset by asset:

  • story text and choice text
  • character images and expressions
  • backgrounds and interface art
  • music and sound effects
  • title art, cover image, screenshots, and project-page graphics
  • translations and promotional copy

For each item, record who made it, what license or permission applies, whether it was generated, and how it should be credited. “Edited by a person” is not enough information to decide whether a generated-content ban applies. If the rule does not clearly cover a mixed or assisted workflow, ask the organizer before submitting. Do not invent an interpretation because the deadline is close.

The same inventory helps outside this one showcase. IFComp asks authors to read the current rules, preview the ballot page, and verify that the links and cover appear as intended. Its handbook also explains that unusual entries with very large file counts may need early coordination. Event rules are part of the release format, not paperwork to scan after the game is done.

Choose the attention pattern, not the largest logo

A ranked competition concentrates attention into a defined judging window. That can produce many plays and comparative feedback, but players arrive with scoring in mind. Deadlines are strict, the release is frozen at important moments, and post-deadline updates may remain visible beside the original judged version.

A feedback event gives unfinished work a reason to be public. The creator should ask a narrow question that the opening can actually answer. Does the first choice reveal the central conflict? Can players understand the protagonist's goal? Does the opening end at a point that creates useful curiosity? Feedback on an excerpt cannot validate unwritten endings.

An unranked showcase offers a different kind of discovery. There is no placement to win. The value comes from appearing in a collection, remaining available to players, and linking the work to longer-lived records such as IFDB or VNDB when appropriate. That asks for stable metadata and a complete work, not a competition pitch disguised as a catalogue entry.

Do not use entry count alone as a demand forecast. A page with many works may bring a healthy audience to the event while still dividing attention among many creators. Treat participation as one discovery path. Keep your own release page, description, support contact, and update history usable after the event link stops sending traffic.

What should a Novelez creator prepare?

Novelez can help with the work before an event, but it does not decide eligibility or register the entry.

Use browser preview to play every route that the public version promises. Share a test link with a small group before freezing the event build. Check the title screen, first choice, endings, audio transitions, mobile layout, and every credit. If the event needs a downloadable PC build rather than a browser experience, Novelez can export to Ren'Py, but that exported project becomes a separate package that needs its own testing.

The event page remains a separate deliverable. A Novelez public link is not automatically an itch.io project page, an IFDB record, a VNDB listing, or a competition registration. Read the host's current submission steps and confirm whether it accepts an external browser link, an uploaded package, or both. Never infer support from the fact that another browser game appears in the event.

Two creators test the public build and organize its cover, credits, and release materials

Prepare a small release folder outside the editor:

  • the exact build or stable public URL being submitted
  • a plain-language description that matches the finished work
  • cover art and screenshots that satisfy the event's content rules
  • complete asset credits and licenses
  • content warnings and accessibility notes
  • a tested support contact
  • the version date and a short change log
  • a copy of the rules as they stood when you entered

Then open the public-facing entry while signed out. Play from the first screen to one ending, check every external link, and confirm that the cover and description describe the same version. A working editor project is not proof that the public package works.

A practical choice for September 2026

The 2026 IntroComp results are useful evidence, but its submission window has passed. IFComp is in judging, so new authors should observe its entries, feedback culture, and schedule rather than try to join late. The Interactive Fiction Showcase is still open for complete 2026 works, but its generated-content ban and credit requirements must be checked against every part of the entry.

That leaves three honest actions.

If the visual novel is incomplete, keep testing the opening and plan for a future feedback event. If it is complete but conflicts with an event's content policy, choose a different discovery route or replace the conflicting material only if doing so is genuinely part of the work, not an attempt to hide its origin. If it is complete, eligible, tested, and properly credited, prepare the event page as carefully as the game itself.

The right event is not the one with the most entries or the nearest deadline. It is the one whose public promise matches the state of your work. Is your current visual novel asking players to help shape an opening, judge a finished release, or discover a complete story that can stand on its own?