Browser delivery
Stop hoping a third-party iframe stays fast. Publish a validated Ren'Py Web build on our stack, smoke it before players see it, keep rollback ready, and give listings stronger delivery truth than a bare embed URL.
Already live on itch? Your store link stays the record. We host the browser runtime you choose to publish.
Product truth, not vanity metrics
What you get
Not generic hosting. A pipeline tuned for Ren'Py Web in the browser, with controls players can feel on the page.
When you publish hosted, the iframe target is our CDN-backed static tree. Fewer cross-origin surprises than bouncing every asset off a random file host.
Each upload becomes a numbered build. Approve, publish, or roll back without rewriting your catalog page from scratch.
We run a bounded startup check on the hosted entrypoint and critical static assets. It is not full QA, but it catches a lot of broken zips early.
Health moves with the build, not with vague player complaints alone. You see when a version looks fragile before you promote it everywhere.
Hosted titles can surface honest trust chips on VNPlay: hosted delivery, verified packaging, smoke-tested startup when the data supports it.
Play and issue signals anchor to a real build id. That is easier to reason about than anonymous embed traffic split across hosts you do not control.
Keep your itch embed on file until you flip delivery. Switch, watch health, roll back if you need to. The path is optional and reversible.
Before and after
Third-party embed hosting is fine until it is not. Here is what changes when PlayVN serves the build.
Pipeline
Orderly, reversible, and boring in the good way.
Drop a Ren'Py Web zip in Studio, or paste a direct HTTPS archive link for assisted import when the source cooperates.
We unpack, scan structure, and refuse obviously broken trees before they waste moderator time or player patience.
A bounded startup probe runs against the hosted entry. Warnings surface early instead of on your Discord at midnight.
Flip the live pointer when you are ready. Older approved builds stay available for rollback.
Players hit a same-origin path we can observe, cache sanely, and explain on the listing with honest trust copy.
Pick your door
Pick the door that matches how far along you already are.
Best for: You have a fresh export from Ren'Py and want the simplest path.
Studio accepts the archive, runs the pipeline, and stages a build for review and publish.
Go to upload flowBest for: You already ship a public HTTPS zip elsewhere and want to mirror it safely.
Assisted import inspects the link with strict bounds, then feeds the same pipeline as a manual upload when the source is compatible.
Open Studio for your titleBest for: Your listing already plays inline from itch or another host.
Keep the embed until you publish hosted. The migration page compares delivery, tracks funnel steps, and never forces a switch.
Studio: pick a game, then MigrationPlayer-facing
Hosted listings can unlock calm trust language on detail and play surfaces: hosted delivery, verified browser packaging, smoke-tested startup when confidence is there, and softer notes when health is mixed. We do not promise rankings. We do give you a cleaner story than a naked iframe.
When delivery is anchored to a build id, session and issue signals are easier to interpret than a soup of third-party embed hits. You still need good habits on your side, but the platform can meet you halfway with version-aware context in Studio.
FAQ
Short answers, honest limits. Ask support if you are blocked on something policy-specific.
Start from a new listing, drop a zip on a game you already own, or open migration on a live embed title. The pipeline is the same once the bits land.