---
title: Publish slides with saved results
description: Replace live questions with snapshots and share a deck without exposing integration credentials.
---

A live presentation and a publicly shared deck have different needs. Use snapshots to preserve results without giving readers access to your speaker token.

## 1. Finish collecting participation

Leave the talk running through built-in feedback collection. When you are done, choose **Finish** in the talk workspace.

Finishing preserves saved results. It does not rewrite snippets already in your slide source.

## 2. Copy fresh snapshots

For each question in the talk question list:

1. Open the output menu and choose **Slidev**.
2. Copy the newly generated output.
3. Replace the corresponding live `questionId` component in your deck.

For a finished talk, the generated output includes the prompt, type, chart where applicable, and saved result data. It no longer relies on the earlier live question reference.

See the [static example](/docs/slidev/reference#static-question). If you run the talk again before generating output, it will generate live references instead.

## 3. Review audience content

Text snapshots include submitted text. Read them before publishing or committing your deck. Remove personal, sensitive, or inappropriate content from the published copy.

Also remove private presenter links, token screenshots, and any material not intended for a public audience.

## 4. Remove live configuration

The current add-on's `VITE_INALIA_API_KEY` can be included in served or built JavaScript. A private `.env` file alone is not enough.

Before preparing public output:

- Remove the integration token and talk-number configuration from the publishing environment.
- Check `~/.inaliarc`, shell variables, and deployment environment settings as well as the project's `.env`.
- Remove connected-talk overview and feedback layouts if they are no longer needed; replace them with ordinary slides and explicit public links.
- Create fresh public output from the token-free configuration. Do not reuse artifacts created with live credentials.
- Delete the dedicated token when no longer needed.

Removing credentials from source does not remove them from an existing artifact, deployment, or Git history. If you already exposed a token, delete it in [Tokens](/profile/tokens) immediately and replace the published output.

## 5. Share the deck

Open the token-free deck without your speaker session and confirm that its snapshots render. Static questions should not receive new responses.

Add the public presentation URL to the talk's **Deck URL** field so attendees can find it. Do not use a private editor or management URL.

For your next live session, duplicate the talk and reconnect a private presenting copy of the deck. Review demo mode and question snippets again using the [pre-flight checklist](/docs/presenting/rehearsal#pre-flight-checklist).