Slicelytics monogram

Share Data with a Link

Copy a link to what is on your screen: your data as filtered, plus the page, properties, filters, and chart. Whoever opens it sees the same view. The data travels inside the link and is never uploaded.

What a Shared Link Carries

A Slicelytics link holds two things: your data, and how to show it. Click Share in the bottom right corner of Explore, Compare, or Visualize, and the link is copied to your clipboard, ready to paste into a chat, an issue, or an email.

  • The data, as filtered: only the items and properties you kept. What is hidden on your screen is left out of the link, so you share no more than you see. Properties the view depends on, such as the x-axis or a value filter, come along even when hidden.
  • The view: the page, the properties shown, value filters such as status="error", and in Visualize the x-axis and the chart type and metric of each property.
  • Both datasets on Compare: a Compare link carries the original and the updated dataset, filtered alike, so your colleague sees the same diff you do.

Your Data Stays in the Link

A shared link looks like this:

https://slicelytics.com/data/visualize?view=<the view>#v=1&data=<your data, compressed>

Everything after # is the link's fragment, which browsers never send to a server, ours included. Slicelytics gzips your data, encodes it as text, and puts it there. The browser that opens the link unpacks the data on its own, so nothing is uploaded and nothing is stored by us.

The view goes before the #, in ?view=, and travels like any web address. It holds property names, filter values, and chart settings, not the dataset.

Opening a Shared Link

Whoever opens the link lands on the same page, with the same data and view, in any modern browser on any computer. From there they can carry on: change the filters, pick another chart, export a PNG, or share their own view back.

If they have Slicelytics installed as an app and already open, the link doesn't replace what they are looking at: the app offers it with a "Show" button. If they are signed out, the link brings them back to its data and view once they have signed in.

How Large Can a Shared Dataset Be?

Browsers limit how long a link can be: Chrome opens links of up to 2 MB. Compression stretches that a long way, as gzip typically makes JSON or CSV 5-10 times smaller, and encoding the result as text adds about a third back. Some chat apps and email clients cut very long links short, so the shorter the link, the safer it travels.

To shorten a link, hide what your colleague doesn't need before you click Share: what is hidden isn't shared. Datasets too large for a link are better shared as files, which open in Slicelytics without leaving your colleague's computer either.

Links from Your AI Agent

AI coding agents such as Claude Code build the same links. Ask your agent to "chart p95 latency per day from runs.csv in Slicelytics", and it compresses the file, unchanged, into a link that opens with the chart already set up. Read more about opening data from AI agents, or build links from your own scripts with the link format reference.

How to Share a View

  1. Open your data: drop a JSON, NDJSON/JSONL, CSV, or TOON file onto Explore, Compare, or Visualize.
  2. Set up the view: pick the properties to show and add value filters. In Visualize, choose the x-axis, the chart type, and a metric.
  3. Click Share: the button in the bottom right corner copies a link to what is on your screen.
  4. Paste the link: send it to your colleague, who opens it on the same view.

Common Questions

Who can see the data in a link?

Anyone who has the link. The data is inside it, so wherever you paste the link keeps a copy, just as if you had attached the file. Share it where you would share the file itself.

Does a link update when my data changes?

No. A link holds the data as it was when you clicked Share. Once the data has changed, share again for a new link.

Does the person I share with need a subscription?

Yes, opening data needs a signed-in Slicelytics subscriber. A link opened before signing in or subscribing survives login and checkout, so they land on it afterwards.