Manage links
CSV import & export
Validate a small batch first and understand why export is not a full-account backup.
Current product guide · Reviewed October 28, 2026
Use the exact format
csv · example
alias,title,destination,tags,expires_at,is_active
launch-guide,Launch guide,https://example.com/guide,launch|email,,1The header order is exact. Use six columns, pipe-separated tags, an empty expiration for no expiry, and 1 or 0 for active status. Quote cells according to normal CSV rules if they contain commas. An empty alias requests a generated code.
Import in two stages
- Select the target workspace and upload a CSV no larger than 256 KB and 100 data rows.
- Run validation/dry run first. Inspect row errors, alias collisions and the capacity result. No links are created by a dry run.
- Submit the actual import only after validation passes. The import uses a transaction; a failed batch must not be treated as a partial success.
- Review the target workspace before retrying an uncertain browser response.
Import does not update existing links. Exporting and re-importing the same aliases will conflict with their reservations. Passwords are not included in the format. Imports are limited to three requests per minute; normal creation and quota rules still apply.
What export includes
Export includes the selected scope’s alias, title, destination, tags, expiration and active status. It does not include API tokens, passwords, analytics, custom-domain certificates, conversations or every account setting. Spreadsheet-sensitive values are prefixed for safer viewing. Review any edited spreadsheet carefully before importing; an export is not an automatic restoration tool.
Still need a hand?
Use Help & support in your dashboard or support@li2.li. Share the action and a sanitized error, never a password, token or private reset link.