Save and share a workspace
Save a workspace to keep its inputs and settings, return to it later, or share a version with someone else. Saving sends the workspace content to regex101 and creates an access link.
- Free
- Included. Account for ownership.
- Pro
- Included. Account for ownership.
- Self-hosted
- Included. Account for ownership.
Save the order example
- Open the first-match example.
- Verify that its input contains only the synthetic order lines.
- If you want account ownership, sign in before saving.
- Open Save & Share, then select Save Workspace.
- Copy the Access Link after the save completes.
- Reopen that link to verify the saved pattern and input.
A save includes supported inputs, settings, the operation, and unit tests. Text Pipeline saves are separate from regex workspaces. They include the pipeline input and layer configuration. Add at least one transformation layer before saving a pipeline. An unfinished layer can be saved as a draft. Local edits do not change a saved version. When signed in, your save mode determines the initial visibility of a new workspace. The save dialog also offers Save title and tags after you edit those account fields.
If you saved without signing in, select Save to account in the save dialog. The sign-in options replace the prompt. After you sign in, the workspace is added to your account.
Workspace and deletion links
| Link | Purpose |
|---|---|
| Access link with a version number | Share a specific saved version. |
Access link with latest instead of the version number | Follow its latest saved version. |
| Delete Link | Remove an anonymously saved workspace. Keep it private. |
| Delete Version Link | Remove the corresponding saved version. Keep it private. |
Replace the version number with latest to create a latest-version link. Keep any editor-mode suffix, such as /substitution.
The workspace identifier stays the same.
Regex links start with /r/. Pipeline links start with /p/.
A stable version is usually better for documentation, review, or a reproducible bug report.
Update or fork
Update Workspace creates a new version within an editable workspace. Fork Workspace creates a separate workspace from the current content. Both actions are in Save & Share for a saved workspace. Updating requires an editable workspace with unsaved changes. A locked workspace restricts changes by other people. Privacy separately controls who can read an account-owned workspace.
Before sharing account-owned work, inspect its privacy and locking controls. An access link does not let another person read a private workspace.
Share without a saved permalink
Copy draft link creates a link to the current pattern, settings, and active test string. It is available in Match and Substitution. Save a workspace to share a pipeline, extraction, or unit-test collection. It puts these fields in the URL without saving a workspace. The application rejects this action when the URL exceeds its supported length.
A URL can appear in browser history, chat previews, and server logs. Do not use a draft link for confidential input. For exact supported fields, read URL parameters.
Publish to the Community Library
Publishing creates a public copy of the current workspace. You can publish before saving a permalink.
- In Manage Workspace, select Publish to Library.
- If you are signed out, sign in to open the publishing form.
- Enter Title and Description. The form uses your workspace title if one exists.
- Enter Author (optional), or leave it blank to appear as Anonymous.
- Select Publish.
Your entry appears in the Community Library. Pipeline publishing requires at least one transformation layer and a complete configuration for every enabled layer.
Recover from a failed save
Keep a local copy of all unsaved workspace content before reloading. Include every input, replacement value, unit test, and pipeline layer. A network or account error can prevent saving even while matching still works. Save troubleshooting explains the next checks.