---
title: Publishing a Subgraph to the Decentralized Network
sidebarTitle: Publish to the Network
---

Once you have [deployed your Subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network.

When you publish a Subgraph to the decentralized network, you make it available for:

- [Curators](/resources/roles/curating/) to begin curating it.
- [Indexers](/indexing/overview/) to begin indexing it.

<VideoEmbed title="How to Publish a Subgraph to Arbitrum" youtube="satdwdbvzAQ" />

Check out the list of [supported networks](/supported-networks/).

## Publishing from Subgraph Studio

1. Go to the [Subgraph Studio](https://thegraph.com/studio/) dashboard
2. Click on the **Publish** button
3. Your Subgraph will now be visible in [Graph Explorer](https://thegraph.com/explorer/).

All published versions of an existing Subgraph can:

- Be published to Arbitrum One. Learn more about The Graph Network on Arbitrum.

- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the Subgraph was published.

### Updating metadata for a published Subgraph

- After publishing your Subgraph to the decentralized network, you can update the metadata anytime in Subgraph Studio.
- Once you’ve saved your changes and published the updates, they will appear in Graph Explorer.
- It's important to note that this process will not create a new version since your deployment has not changed.

## Publishing from the CLI

As of version 0.73.0, you can also publish your Subgraph with the [`graph-cli`](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli).

1. Open the `graph-cli`.
2. Use the following commands: `graph codegen && graph build` then `graph publish`.
3. A window will open, allowing you to connect your wallet, add metadata, and deploy your finalized Subgraph to a network of your choice.

![cli-ui](/img/cli-ui.png)

### Customizing your deployment

You can upload your Subgraph build to a specific IPFS node and further customize your deployment with the following flags:

```
USAGE
  $ graph publish [SUBGRAPH-MANIFEST] [-h] [--protocol-network arbitrum-one|arbitrum-sepolia --subgraph-id <value>] [-i <value>] [--ipfs-hash <value>] [--webapp-url
    <value>]

FLAGS
  -h, --help                   Show CLI help.
  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
  --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
  --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                               <options: arbitrum-one|arbitrum-sepolia>
  --subgraph-id=<value>        Subgraph ID to publish to.
  --webapp-url=<value>         [default: https://cli.thegraph.com/publish] URL of the web UI you want to use to deploy.

```

## Adding signal to your Subgraph

Developers can add GRT signal to their Subgraphs to incentivize Indexers to query the Subgraph.

- If a Subgraph is eligible for indexing rewards, Indexers who provide a "proof of indexing" will receive a GRT reward, based on the amount of GRT signalled.

- You can check indexing reward eligibility based on Subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).

- Specific supported networks can be checked [here](/supported-networks/).

> Adding signal to a Subgraph which is not eligible for rewards will not attract additional Indexers.

> If your Subgraph is eligible for rewards, it is recommended that you curate your own Subgraph with at least 3,000 GRT in order to attract additional indexers to index your Subgraph.

The Sunrise Upgrade Indexer ensures the indexing of all Subgraphs. However, signaling GRT on a particular Subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.

When signaling, Curators can decide to signal on a specific version of the Subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.

Indexers can find Subgraphs to index based on curation signals they see in Graph Explorer.

![Explorer Subgraphs](/img/explorer-subgraphs.png)

Subgraph Studio enables you to add signal to your Subgraph by adding GRT to your Subgraph's curation pool in the same transaction it is published.

![Curation Pool](/img/curate-own-subgraph-tx.png)

Alternatively, you can add GRT signal to a published Subgraph from Graph Explorer.

![Signal from Explorer](/img/signal-from-explorer.png)

Learn more about [Curating](/resources/roles/curating/) on The Graph Network.
