Guide6 min read

Replit Portfolio Demo Video

Show the repl running, not a screenshot of it.

Turn a public Replit app into a portfolio entry that shows it running, with a wake up step most writeups skip.

See how it worksYour first 60 seconds of video are free, with a watermark.
Verify your email to download it.

A portfolio entry built on Replit has one job a screenshot cannot do: it has to prove the app runs. Anyone can crop a static image into a card and caption it as a finished project. A person reading a portfolio for hiring or contract work has seen enough of those to discount them on sight. What they want is confirmation that the thing behind the link actually does something, and the fastest way to give them that is a short video of the app doing it.

Replit's own shape makes this both easier and slightly trickier than it sounds. Every project has a live webview pane next to the code, and a public repl exposes that same running app at a URL a visitor can open directly. That is the part that helps: there is always something real to point a camera at, not a build you have to stand up separately. The part that trips people up is that a repl without an active deployment goes idle after a period with no traffic, and the first request after that has to wake it before anything renders. A portfolio video recorded against a cold repl can open on a spinner instead of the screen it was supposed to prove.

Which repl should go in the portfolio?

Pick the repl that shows the most legible single screen, not the most feature dense one. A hiring manager or a client skimming ten portfolio entries in a row will give each one a few seconds before deciding whether to keep watching. The project that shows one recognizable interaction, such as filtering a list or submitting a form and seeing the result, reads faster than a project that tries to walk through five different pages.

The repl needs to be public so both a viewer and a rendering tool can reach it. If the code lives in a private repl for a reason, consider whether a stripped down public copy with the same interaction can stand in for the portfolio entry without exposing anything that should stay closed.

What to check	Why it matters for a portfolio entry
Repl visibility	A private repl cannot be opened by a viewer or a rendering tool
Webview state	The screen you want to show has to actually load in the webview pane
Example data	Content should be prepared and legible, not a blank state or personal data

Why does the repl need to be woken up first?

This is the detail most writeups about demo videos skip because it is specific to how Replit runs a free or lightly used repl. A repl that has not received traffic for a while goes idle, and the next visitor's request is what wakes it back up. That wake up takes a few real seconds, during which the webview shows a loading state rather than the app.

If a render request hits a cold repl, the recorded result can capture exactly that loading state at the moment meant to be the portfolio's best evidence. The fix is procedural, not technical: open the repl yourself, let the webview finish loading, confirm the screen you intend to show is the one that appears, and only then request the render. This single habit prevents the most common reason a Replit based demo comes back looking unfinished when the app itself is not.

A repl that has gone idle needs a moment to wake before the page you want to show even loads, and no amount of hint writing fixes that after the fact. Treat the wake up step as part of preparation, the same way you would check a route is reachable on any other platform. This matters more for a portfolio than it does for an internal walkthrough, because a portfolio entry is often the first and only interaction a stranger has with the project. A recruiter or a client browsing several entries back to back will not know the repl was cold, only that the video they clicked on opened with a spinner, and two minutes spent opening the repl beforehand removes that risk entirely.

What should the one line hint say?

Name the screen, the action, and the result. "Open the dashboard, add a task, and show it in the list" gives a rendering tool a specific target rather than an open ended request to summarize the app. A vague hint like "show the project" invites a generic walkthrough that does not match what a portfolio needs, which is one convincing moment rather than a tour.

Pick a public repl whose webview loads the specific screen you want a visitor to judge.
Open the repl once yourself so it is already awake before you request the render.
Write a one line hint naming the screen, the action, and the result you want the portfolio entry to prove.

Keep the language in the hint consistent with what actually appears on screen. If the app calls something a board, do not describe it as a dashboard in the hint. GogoScreen accepts a web app URL and this one line hint, then returns a narrated MP4 with captions, cursor smoothing, click zooms, and dead air removed. It can use a supplied demo account when the screen you want sits behind a login, with the credential encrypted, used for that one render, then deleted. When a storyboard is planned first, the credentials are kept encrypted for that session and deleted at most two hours after their last use.

How does this differ from other builder platforms?

Replit's always visible webview and repl based URL are specific to how that platform runs projects, which is different from a platform where the running app only exists after an explicit deploy step. The Bolt landing page video guide and the Bolt Product Hunt launch video guide cover a platform where the preview runs inside a sandboxed browser session until a deploy step publishes it somewhere stable. A Bolt share with a client guide and a Bolt portfolio demo guide walk through the same portfolio question for that different setup.

For the review side of a Replit build, the Replit app review walkthrough guide covers what a reviewer needs to see rather than what a portfolio visitor needs to see, which is a narrower and different job. If a repl is not the right format for a given moment, automated screen recording for a web app explains the URL and hint workflow in more general terms, and the product demo GIF alternative guide makes the case for a narrated video over a silent loop.

What happens if the render does not come back clean?

Not every render succeeds on the first try. Roughly one render in five fails or needs a retry, and a portfolio entry deserves the same review as any other page asset before it goes live. Check the result against the screen and action named in the hint rather than assuming a returned file is automatically correct.

Confirm the repl was awake and loaded the intended screen before the render started.
Compare the finished video against the hint's stated action and result.
Re-request the render with a narrower hint if the first attempt drifts off the intended screen.

If a render fails outright, the demo video render failure guide covers what to change before trying again. A portfolio built around a project still taking shape can also draw on the beta launch demo video guide for how much polish a pre launch entry actually needs, and the AI agent pull request demo video guide is useful when the more relevant proof is a specific code change rather than the whole app. For a direct comparison of tools that produce this kind of asset, see GogoScreen versus Demosmith. Review pricing, browse the rest of the guides and comparisons, or start from the GogoScreen homepage to try the URL and hint workflow on your own repl.

Clarifications

Before you start

Does a portfolio entry need the repl to be public?

Yes. A private repl cannot be opened by a viewer or by a rendering tool, so a portfolio entry needs a public repl with a working webview before anything else is decided.

Why does a repl need to be opened before recording?

A repl that has been idle goes to sleep, and the first request after that wakes it. Opening it yourself first means the render shows the app, not a loading screen.

Should the repl contain real data?

No. A portfolio repl should hold prepared, non sensitive example data that makes the shown screen legible, not a personal account or anything private.

Paste a URL, describe one flow, and get a demo video of your web app.

Your first 60 seconds of video are free, with a watermark. Verify your email to download the video.

View pricing Read the guides