---
title: How to alias a preview deployment using the CLI
description: Learn how to automatically alias a Vercel preview deployment.
url: "https://vercel.com/kb/guide/how-to-alias-a-preview-deployment-using-the-cli"
published: 2025-11-03
last_updated: 2026-10-02
authors: Lee Robinson
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

You can use Vercel CLI to create Preview Deployments and can also use the Vercel CLI to alias a URL to that deployment. Each preview deployment has a unique URL. The latest Preview Deployment is automatically aliased to a URL, ensuring you'll have a stable URL pointing to the last Preview Deployment.

This covers adding another URL to the Deployment using the [alias command](https://vercel.com/docs/cli/alias). In this example we use the Vercel CLI to do a deployment using the `vercel deploy` command. A successful deployment writes the deployed URL to the [Standard Output](https://vercel.com/docs/cli/deploy#standard-output-usage) so you can use it in later commands.

As an example:

```bash
url="$(vercel deploy)"
vercel alias set "$url" your-alias.app
```

## Example with GitHub Actions

In [this article](https://vercel.com/guides/how-can-i-use-github-actions-with-vercel) we cover how to deploy using GitHub Actions. We can expand that example and alter the last couple of lines to do that auto-aliasing.

To set this Action up, please refer back to the [original article](https://vercel.com/guides/how-can-i-use-github-actions-with-vercel). Then change the last lines as below:

```text
name: Vercel Preview Deployment
env:
  VERCEL_ORG_ID: ${{ secrets.VERCEL_ORG_ID }}
  VERCEL_PROJECT_ID: ${{ secrets.VERCEL_PROJECT_ID }}
on:
  push:
    branches-ignore:
      - main
jobs:
  Deploy-Preview:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Install Vercel CLI
        run: npm install --global vercel@latest
      - name: Pull Vercel Environment Information
        run: vercel pull --yes --environment=preview --token=${{ secrets.VERCEL_TOKEN }}
      - name: Build Project Artifacts
        run: vercel build --token=${{ secrets.VERCEL_TOKEN }}
      - name: Deploy Project Artifacts to Vercel
        run: |
          url="$(vercel deploy --prebuilt --token=${{ secrets.VERCEL_TOKEN }})"
          vercel alias --token=${{ secrets.VERCEL_TOKEN }} set "$url" your-alias.app
```

## More Vercel CLI guides

- [Build a fullstack app with Next.js 16 and Prisma Postgres](/kb/guide/nextjs-prisma-postgres): Create a fullstack blog with the Next.js App Router, Prisma, Sign in with Vercel, Prisma Postgres from the Vercel Marketplace, and deploy it to Vercel.
- [How can I run end-to-end tests after my Vercel Preview Deployment?](/kb/guide/how-can-i-run-end-to-end-tests-after-my-vercel-preview-deployment): Learn how to use the Vercel CLI in combination with your CI/CD provider to run end-to-end tests for every code change.
- [The Complete Guide to Vercel Connect](/kb/guide/vercel-connect): Use Vercel Connect to call provider APIs like Slack, GitHub, Linear, Microsoft, Discord, Snowflake, and Salesforce from your agents and services with short-lived, scoped tokens instead of long-lived secrets.