01
Compress from the workspace
Upload media, choose a preset, and follow the real processing job from one focused workspace.
Media infrastructure for uploads and APIs
Make heavy mediaeasier to deliver.
Compress video, image, and audio for Discord, everyday sharing, and developer pipelines. Run batches in the cloud, get notified when long jobs finish, and keep control of where your files live.
Connected media pipeline
Import from your device, Google Drive, or Dropbox. Dislify applies the same secure processing before delivering the result wherever your workflow needs it.
Private processing
Import from
Local uploadChoose media from your device
Google DriveBrowse connected Drive files
DropboxImport without downloading first
OptimizeReady
Dislify media core
One secure pipeline for every source and preset.
ImageVideoAudio
Deliver to
DownloadReceive the optimized file
Share linkSend a secure expiring link
WebhookContinue an automated workflow
Media types
Video · Image · Audio
Connected sources
Device · Drive · Dropbox · S3
Developer platform
API · SDK · Webhooks
Built for
Bots · Apps · Workflows
Try the workflow
Compress media. See the difference.
Upload a file, choose a preset, and download the optimized result through the same processing system used by the dashboard and API.
Choose from eight presets or set a custom target file size.
Background workers continue after the browser upload finishes.
Signed-in users can receive completion and failure emails.
Use the same lifecycle through API keys and webhooks.
Compression workspace
Media optimizerUpload one file, a batch, folder, ZIP archive, or connected cloud media.
One system, three surfaces
One pipeline. Three ways to use it.
Compress through the workspace, developer API, or automated webhook workflows—all powered by the same processing system.
02
Automate through the API
Use the REST API or @dislify/sdk to submit media, inspect usage, and connect compression to your product.
03
React through webhooks
Receive signed job events, test endpoints, rotate secrets, and keep downstream systems synchronized.
Discord bot guide
Give your server a real media command.
Build a bot that accepts attachments, sends them through Dislify with the Discord preset, reports progress, and returns the optimized output or a secure share link.
Receive /compress
01Accept an image, video, or audio attachment from Discord.
Submit the media
02Send the attachment through the SDK or REST API.
Report progress
03Edit the deferred response while Dislify processes the job.
Deliver the result
04Return the optimized file or its secure share URL.
Bring your own storage
Keep the Dislify pipeline. Choose where the files live.
Use included managed storage, then connect your own S3-compatible bucket when you need more capacity, longer retention, or direct control over storage lifecycle.
Included managed storage
Pro includes 8 GB and Unlimited includes 25 GB of Dislify-managed storage for active jobs and retained results.
Bring your own S3
Connect AWS S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, or another public S3-compatible endpoint.
Choose routing and retention
Send every new upload to your bucket or use it for overflow, then choose a retention period or keep files indefinitely.
Pro: 8 GB managed · Unlimited: 25 GB managed
BYO S3 supports full routing or overflow routing, plus custom retention for new uploads. Your bucket stays under your account and billing.
Operational depth
Built for the full media workflow.
Authentication, plan limits, queues, storage, notifications, developer APIs, and secure delivery work together across the compression lifecycle.
Account access
Authentication, verification, sessions, and account controls.
Usage controls
Plan-aware limits, API quotas, managed storage, and real processing metrics.
Async processing
Fair queues, dedicated workers, progress updates, background jobs, and email completion alerts.
Secure delivery
Private storage, signed uploads, protected downloads, share links, and verified callbacks.
Integrations
Bring media in without the extra download step.
Connect cloud storage, your own S3-compatible bucket, or move directly into code. Every source feeds the same private Dislify processing pipeline.
Google Drive
Import media or reclaim space by saving verified compressed copies back to Drive.
Dropbox
Compress Dropbox media in place, with replacement available only after explicit approval.
Your S3 bucket
Connect S3-compatible storage on Pro or Unlimited for overflow, custom retention, or full routing.
@dislify/sdk
Handle authentication, signed uploads, retries, polling, and typed results.
Cloud storage cleanup
Pro and Unlimited workspaces can compress selected Drive and Dropbox media, save a smaller copy, or explicitly approve replacing the original.
Use cases
From one Discord clip to a full media pipeline.
Start with manual compression and grow into batch jobs, cloud storage, and automated delivery without changing products.
01
Discord uploads
Shrink clips and media that exceed channel upload limits.
Creators02
Community bots
Compress user attachments and return results automatically.
Automation03
AI-generated assets
Optimize generated images and media before production delivery.
Developers04
SaaS upload flows
Process customer media before long-term storage or delivery.
Products05
Cloud storage cleanup
Reclaim Google Drive or Dropbox space without automatic replacement.
Pro06
Long-retention archives
Route new uploads to your own S3-compatible bucket and control how long files stay there.
StorageQuestions
Everything important, without the marketing fog.
A practical view of what Dislify processes and how it fits into real workflows.
What file types can Dislify process?+
Dislify is designed for common video, image, and audio formats. Exact support depends on the active worker configuration and selected compression mode.
Is Dislify only for Discord?+
No. Discord-friendly compression is a core use case, but the same pipeline supports creator uploads, web products, bots, storage workflows, and developer APIs.
Can I automate compression?+
Yes. Developer access includes the REST API, @dislify/sdk, asynchronous jobs, usage visibility, and signed webhook events.
Where are processed files stored?+
Dislify uses private object storage and protected delivery URLs. Managed files are retained for 1 day on Free, 30 days on Pro, and 90 days on Unlimited. Pro and Unlimited can also connect their own S3-compatible bucket for custom retention and storage routing. BYO S3 is available from Account settings.
Can Dislify free up Google Drive or Dropbox storage?+
Yes. Pro and Unlimited workspaces can compress selected cloud media and save smaller copies back to Google Drive or Dropbox. Replacing originals is optional, requires explicit approval, and only runs after the output is verified to be smaller.
Ready when you are
Compress the file now. Automate the next thousand later.
Create an account for the workspace, connect your storage, or explore the developer API, guides, and webhook workflow.