Share JSON via Compressed URL
Learn how to share your JSON data, editor state, or transformation config with teammates using DataLensia's stateless sharing.
Last updated:
DataLensia lets you share your entire working state โ data, transformations, and configurations โ through a single URL. No accounts, no uploads, no databases.
๐ฉ The Use Case
You've set up a complex transformation in the Transform Builder and want your colleague to review it. Instead of exporting files and writing instructions, you can share a single link.
๐ ๏ธ How to Share
You can share your work from both the integrated Workspace and individual Standalone Tools.
Sharing from a Workspace
- Open or create a Workspace from the Tools panel.
- Load your JSON data and optionally configure transformations, comparisons, etc.
- Click the Share icon in the top-right of the workspace header.
- A compressed URL is generated and copied to your clipboard.
- Send the link to your colleague via Slack, Teams, or email โ they can open it and see the exact same state you shared.
Sharing from Standalone Tools
- Open any standalone tool (e.g., Editor, Comparator, Mermaid).
- Input your data or configure your diagram, diff, or conversion.
- Click the Share icon (๐) found in the tool's action bar or toolbar.
- Send the generated link to your colleague โ they will see your exact data and configuration instantly.
โ๏ธ How It Works Under the Hood
- Serialize: Your data and configuration are serialized to a JSON string.
- Compress: The string is compressed using multiple algorithms simultaneously:
- V1: LZ-String (URI-safe) โ best for very small payloads.
- V2: Pako Deflate + Base64url โ best for general data (40-60% smaller than V1).
- V3: Columnar encoding + Pako Deflate โ best for arrays of objects (tabular data).
- V4: Columnar + Key aliasing + Pako Deflate with Custom Static Dictionary โ best overall, producing up to 15% shorter URLs for any workspace configuration.
- Select: The shortest output among V1, V2, V3, and V4 is automatically selected.
- Fragment: The result is placed in the URL hash fragment (
#), meaning it's never sent to the server.
When someone opens the link:
- The hash fragment is read.
- The version prefix is detected (V1 has no prefix, V2 starts with
2., V3 starts with3., V4 starts with4.). - The string is decoded and decompressed.
- The workspace state is reconstructed locally.
๐ Size Limits
| Scenario | Approximate Limit |
|---|---|
| Small JSON (< 5KB) | Always works |
| Medium JSON (5-50KB) | Works on most platforms |
| Large JSON (50-100KB) | May be truncated by messaging apps |
| Very large JSON (> 100KB) | Use file export instead |
Tip: Most messaging platforms (Slack, Teams, Discord) support URLs up to ~4000 characters. For larger payloads, DataLensia will warn you and suggest alternatives.
๐ก๏ธ Privacy Guarantee
- Your data is never sent to DataLensia's servers.
- The compressed data lives only in the URL fragment.
- URL fragments are not included in HTTP requests โ they stay in the browser.
๐ Try it now
Open or create a Workspace, load any JSON, and click the Share icon in the top-right of the workspace header to generate your first compressed link.