> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstream.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Saved Queries

> Save, organize, and manage your frequently used GraphQL queries locally in the IDE

## Overview

The GraphQL IDE lets you save queries to your browser for quick access later. Saved queries persist across browser sessions and appear in the sidebar's **Saved** tab, giving you a personal library of go-to queries without needing external tools.

***

## Saving a Query

<Steps>
  <Step title="Write or load a query">
    Enter a query in the editor, or load one from the [templates](/en/graphql/ide/query-templates).
  </Step>

  <Step title="Click Save Query">
    Click the **Save Query** button in the toolbar. A dialog appears with two fields:

    * **Title** (required) — A descriptive name for the query
    * **Tags** (optional) — Comma-separated labels for organization (e.g. `solana, dex, monitoring`)
  </Step>

  <Step title="Confirm">
    Click **Save**. The query is stored locally and immediately appears in the sidebar **Saved** tab.
  </Step>
</Steps>

<Tip>
  Use descriptive titles that include the chain and Cube name, e.g. "Solana — Latest Raydium Trades" or "ETH — USDC Top Holders". This makes queries easy to find as your collection grows.
</Tip>

***

## Loading a Saved Query

1. Open the sidebar (**Ctrl/Cmd+B**)
2. Switch to the **Saved** tab
3. Click on any saved query to load it into the editor

The query text, variables, and headers are all restored to the state when the query was saved.

***

## Deleting a Saved Query

To delete a saved query:

1. Open the sidebar and switch to the **Saved** tab
2. Hover over the query you want to remove — a **delete** icon appears
3. Click the delete icon to remove the query

<Note>
  Deletion is permanent. There is no undo — once deleted, the query cannot be recovered.
</Note>

***

## Storage Details

| Property              | Detail                                                            |
| :-------------------- | :---------------------------------------------------------------- |
| **Storage mechanism** | Browser `localStorage`                                            |
| **Persistence**       | Survives page refreshes and browser restarts                      |
| **Scope**             | Per-browser, per-origin (same domain)                             |
| **Sync**              | Not synced across devices or browsers                             |
| **Clearing**          | Clearing browser data or `localStorage` removes all saved queries |

<Info>
  Saved queries are stored entirely in your browser's `localStorage`. They are **not** sent to any server and are not accessible from other devices. If you need to share a query, use the [Code Export](/en/graphql/ide/code-export) feature to generate a portable snippet.
</Info>

***

## Organizing with Tags

Tags help you categorize and filter saved queries as your collection grows. Some recommended tagging strategies:

<AccordionGroup>
  <Accordion title="By chain">
    Use chain-specific tags like `solana`, `ethereum`, `bsc` to quickly filter queries for a particular network.
  </Accordion>

  <Accordion title="By Cube">
    Tag queries with the Cube name: `dextrades`, `transfers`, `ohlc`, `holders`, etc.
  </Accordion>

  <Accordion title="By use case">
    Functional tags like `monitoring`, `analysis`, `debug`, `dashboard` indicate the query's purpose.
  </Accordion>

  <Accordion title="By token or project">
    Tag with specific project names or token symbols: `usdc`, `bonk`, `raydium`, `uniswap`.
  </Accordion>
</AccordionGroup>

<Tip>
  There's no limit on the number of tags per query. Combine multiple tagging dimensions — e.g. `solana, dextrades, raydium, monitoring` — for maximum searchability.
</Tip>

***

## Best Practices

* **Save iteratively** — Save working versions of queries as you refine them. Use versioned titles like "OHLC v1", "OHLC v2" if needed.
* **Clean up regularly** — Delete queries you no longer use to keep the sidebar manageable.
* **Export before clearing** — If you plan to clear browser data, export important queries as code snippets first via [Code Export](/en/graphql/ide/code-export).
* **One query per concern** — Avoid saving monolithic queries that do too much. Smaller, focused queries are easier to reuse and compose.