Build
Run npm run build in the Astro project and use dist/ by default, or the static output directory set in the project configuration.
All use cases
For an Astro site build
Preview an Astro static build online.
Astro source becomes browser-ready after your local build. When the next step is review, package the generated dist directory as a ZIP and publish that static output as a link. HTMLShare does not run Astro or turn the source project into a server-rendered app.
Review lens
The dist folder is the review artifact
The preview starts with what Astro emitted. Verify the generated files at the location and widths your reviewers will use.
Assets
Keep index.html, _astro assets, public files, images, fonts, and other generated resources in the ZIP with their relative paths.
Paths
Check internal links and any configured base path or asset prefix against the preview URL before sharing.
A real moment for the page
A browser link makes the next conversation concrete.
Landing page review
Let a client or teammate inspect the generated Astro pages without installing dependencies or opening the source project.
Content and responsive QA
Check rendered copy, mobile layout, links, images, fonts, and other static assets in the browser preview.
Static handoff
Share the exact dist snapshot while the team decides where the approved site belongs after review.
Why this handoff works
Keep the useful part close to the artifact.
Review the generated output
The link represents the files Astro produced, not a source folder that still needs npm install, a dev server, or a build step.
Keep asset paths together
A complete ZIP preserves the generated HTML, _astro bundles, public files, and other relative resources that the page needs.
Separate preview from runtime
Use the link to review static pages. SSR, adapters, server rendering, backend integrations, and authentication need another environment.
A three-step workflow
From the right files to the right reaction.
- 01
Build locally
Run the Astro build command in your normal local or CI workflow and locate dist/, or the custom output directory configured for the project.
- 02
Zip the static output
Package the generated contents with index.html, _astro, public files, images, fonts, and other assets. Do not upload src as a substitute for the build.
- 03
Open and review
Check routes, base path, assets, responsive layout, and client-side interactions in a fresh browser, then send the preview link for review.
Know the boundary
A preview is useful because it is honest.
HTMLShare publishes browser-ready static output. Keep builds, source tools, private access, live data, and production operations in the systems built for them.
HTMLShare does not run Astro
Build the project in your local or CI workflow first. HTMLShare publishes the resulting browser-ready static output.
Static browser files only
SSR, adapters, server rendering, server endpoints, backend logic, authentication, and live data are outside this static preview.
Move approved work onward
HTMLShare is for the review stage. Use the production environment built for your site's runtime, domain, monitoring, and release operations.
Keep exploring
The next useful page is nearby.
Before you publish
Astro static build preview FAQ
Can HTMLShare build my Astro project?
No. Run the Astro build in your local or CI workflow, then upload the generated static output, usually the dist directory.
What should I upload for an Astro preview?
Zip the generated dist contents with index.html, _astro assets, public files, images, fonts, and any other resources the built pages reference.
Does an Astro SSR project or adapter work in HTMLShare?
No. This workflow publishes browser-ready static files only. SSR, adapters, server rendering, server endpoints, backend logic, and authentication require another runtime.
Can I use an Astro preview as production hosting?
No. Use the preview for review, then move approved output to the production environment that provides the site's runtime and ongoing operations.
Ready for the next review
Put the current page in front of the right person.
Create a noindex preview link for the static HTML or ZIP project, then move approved work to production when it is ready.