How to Share a Next.js Project Without Pushing to GitHub

Q: Can I share multiple versions of the same project?

Yes. Each time you run sher link , you get a new unique URL. This means you can deploy different branches or variations of your project and share each one separately, which is useful when comparing design options or gathering feedback on multiple approaches.

February 2026

The standard way to deploy a Next.js project is through Vercel: you push your code to GitHub, Vercel detects the change, builds the project, and deploys it. It works well for production, but there are plenty of situations where you just want to share what you have right now without going through the full commit-push-deploy cycle.

Maybe you are halfway through a redesign and want a client to see the progress. Maybe you are comparing two approaches and want to send both to your team for feedback. Or maybe you just finished a prototype and want to pull it up on your phone before committing anything. In all of these cases, pushing to GitHub feels like too much ceremony for what should be a quick share.

How sher handles Next.js

sher is a CLI that builds your frontend project and uploads it to a temporary preview URL. When you run it in a Next.js project directory, it detects the framework automatically, runs next build with static export, uploads the output, and gives you a shareable link in seconds.

Here is how to set it up and use it.

Step 1: Install sher

Install the CLI globally with npm:

npm i -g shersh

This gives you the sher command available anywhere on your system.

Step 2: Run `sher link` in your project

Navigate to your Next.js project directory and run:

sher link

sher detects that you are in a Next.js project, runs the build using your project's package manager, and uploads the resulting static files. The whole process typically takes under a minute.

$ sher link

  sher - share your work

  framework  Next.js
  building   npm run build
  files      24 files (1.2MB)
  uploading  ...

  https://a8xk2m1p.sher.sh  (copied)
  expires 2/19/2026, 11:00 AM

Step 3: Share the URL

The URL is copied to your clipboard automatically, so you can paste it directly into Slack, email, or a text message. Anyone with the link can view the site in their browser without installing anything or having access to your repository.

A note on static export

sher works with Next.js by using the static export mode (output: "export" in your Next.js config). This means it generates plain HTML, CSS, and JavaScript files that can be served from anywhere without a Node.js server running behind them.

For most frontend preview use cases, static export covers exactly what you need: pages render correctly, client-side navigation works, and assets load as expected. However, server-side features like API routes, server-side rendering, middleware, and server actions will not work in the preview since there is no Node.js runtime behind the URL. If your project relies heavily on these features, the preview will show the static portions of your site but not the dynamic server-rendered parts.

This makes sher a great fit for marketing pages, landing pages, documentation sites, portfolios, and any project where the frontend is the main thing you want to show someone.

Works with other frameworks too

sher is not limited to Next.js. It auto-detects and builds projects using Vite, Astro, Create React App, and other popular frontend frameworks. The workflow is identical regardless of the framework: run sher link and get a preview URL. If you work across multiple frameworks, you only need to remember the one command.

FAQ

Do I need to configure Next.js for static export before using sher?

Sher handles the static export configuration automatically during the build process. You do not need to manually add output: "export" to your next.config file. If your project already has this setting, sher will use it as-is.

Will my Next.js API routes work in the preview?

No. Since sher serves static files without a Node.js backend, API routes, server-side rendering, middleware, and server actions will not function in the preview. The static portions of your site, including all client-side rendered pages and assets, will work normally.

How long does the preview URL stay active?

The duration depends on your account tier. Anonymous users get 6-hour previews, logged-in users (free, via sher login) get 24-hour previews, and Pro users get up to 7 days. For most quick-share scenarios, the free tier provides plenty of time for someone to review your work.

Can I share multiple versions of the same project?

Yes. Each time you run sher link, you get a new unique URL. This means you can deploy different branches or variations of your project and share each one separately, which is useful when comparing design options or gathering feedback on multiple approaches.

Get started

Install sher globally:

npm i -g shersh