# Managing snippets — the Vault screen
**Code vault** in the left nav. Every snippet you have, whether each is switched on, and the one setup step that decides whether any of them reach your storefront.
## Turn on the Snapty app embeds
**If a snippet is saved and your storefront looks exactly the same, start here.**
Snapty adds two app embeds to your theme. They are the only path from the Vault to a page:
| Embed | Delivers |
| --- | --- |
| **Vault code — head** | Snippets placed in `
` |
| **Vault code — body** | Snippets placed before `` |
Shopify turns app embeds **off by default** when any app is installed, and Snapty cannot switch them on for you.
In your Shopify admin, **Online Store → Themes**.
On your **live** theme, click **Customize**.
Open **App embeds** in the left sidebar.
Turn on **Vault code — head** and **Vault code — body**.
Click **Save**.
Turn on both. Turning on one means every snippet with the other placement goes nowhere, and nothing on the storefront says so.
**How Snapty tells you they are off:** a banner on the Vault screen naming which embed is off, with a link into the theme editor; a note on the placement step when you add a snippet; and the Vault card on the dashboard.
**If the embed is not in your theme at all**, the editor shows nothing to turn on. Opening the theme editor for your live theme is what adds it; once it is there, the steps above apply.
**When you publish a different theme**, turn the embeds on in that theme too. Your snippets are unchanged — they are in the Vault, not in either theme.
## The list
| Column | What it holds |
| --- | --- |
| **Name** | The name you gave it. Only you see it |
| **Where it loads** | **In the head** or **In the body** |
| **Kind of code** | Script · CSS · HTML · Meta and link tags |
| **Status** | **Active** — delivered on every page load. **Inactive** — kept, delivered nowhere |
Click a row to open the snippet — see [Adding and editing a snippet](https://docs.foxecom.com/snapty-app/code-vault/adding-and-editing-a-snippet).
## Search
By name, at the top of the screen. Names never reach the storefront, so name snippets for how you will look for them.
## Turn on / Turn off
From the row, or from the snippet's own screen. Snapty confirms first:
> **Turn off *Meta Pixel*?**
> It stops loading from the next page load. Your code is kept exactly as you saved it, so you can turn it back on at any time.
- **Turn off** — delivery stops from the next storefront page load. Nothing is deleted; the code and its history are kept. This is the right action for *"I want this to stop, but I might want it back"*.
- **Turn on** — delivery resumes from the next page load. Nothing else about it changes.
## Select several
Select multiple rows to **turn on**, **turn off** or **delete** them in one action. Each bulk change republishes your storefront once. Bulk delete confirms first:
> This removes them and their code for good. If you only want them to stop running, turn them off instead — that keeps everything.
## The budget line
*N KB of the shared budget.* A page-weight guide, not a limit: everything active loads on every page, so the line shows what your snippets add up to. Going past it does not stop a save — it means every page carries the extra weight. Turning a snippet off takes it out of the count.
## Why this is safe
Vault code lives outside your theme files. It keeps working through a theme update, and through a switch to an entirely different theme. Snapty never writes any of it into your theme.