If you share files regularly from your terminal, the EasySend CLI tool lets you upload and share files with a single command. No browser, no drag-and-drop, no manual copy-paste. Just easysend report.pdf and you get a shareable link.
Installation
Install the CLI with one command:
curl -fsSL https://easysend.co/cli/install.sh | bash
This downloads the easysend binary and adds it to your PATH. Works on Linux and macOS. No dependencies, no runtime, no package manager needed.
Basic Usage
# Upload a single file
easysend report.pdf
# Upload multiple files (bundled under one link)
easysend design.psd mockup.png spec.pdf
# Upload and copy link to clipboard
easysend photo.jpg --copy
# Upload with JSON output (for scripting)
easysend data.csv --json
# Pipe from stdin
cat backup.sql | easysend --name backup.sql
Every command returns a shareable link. The --json flag outputs structured data including the share URL, upload token and file metadata.
Scripting Examples
Upload and Send via Slack Webhook
#!/bin/bash
RESULT=$(easysend monthly-report.pdf --json)
URL=$(echo "$RESULT" | jq -r '.share_url')
curl -X POST "$SLACK_WEBHOOK" \
-H "Content-Type: application/json" \
-d "{\"text\":\"Monthly report ready: https://easysend.co$URL\"}"
Daily Database Backup
#!/bin/bash
# Run as cron: 0 2 * * * /opt/scripts/backup-share.sh
DATE=$(date +%Y-%m-%d)
mysqldump mydb | gzip > "/tmp/backup-$DATE.sql.gz"
LINK=$(easysend "/tmp/backup-$DATE.sql.gz" --json | jq -r '.share_url')
echo "Backup shared: https://easysend.co$LINK" >> /var/log/backups.log
rm "/tmp/backup-$DATE.sql.gz"
CI/CD Build Artifact Sharing
# In GitHub Actions or GitLab CI
- name: Share build artifact
run: |
RESULT=$(easysend dist/app-v$VERSION.zip --json)
echo "Download: https://easysend.co$(echo $RESULT | jq -r '.share_url')"
Advanced Options
--info CODE- get bundle info (file list, download count, expiry)--delete TOKEN FILE_ID- delete a file from an existing bundle--notify [email protected]- receive download notifications--password SECRET- add access password to the upload
CLI vs API vs Web
- CLI - best for terminal workflows, scripting, cron jobs and CI/CD pipelines
- API - best for application integration, custom upload forms and automated systems
- Web - best for one-off sharing with non-technical recipients
All three use the same backend. Files uploaded via CLI are accessible via the same share links as web uploads. The CLI simply wraps the REST API in a convenient command-line interface.
Full CLI documentation is at /cli. For API integration, see the API integration guide.
Install the CLI