# Yungle

> Yungle is a private, EU-hosted file transfer service: an alternative to WeTransfer for
> people who need their files to stay in Europe. Free anonymous transfers up to 10 GB
> per transfer, unlimited in number, kept for 7 days, with no account and no ads.
> Paid plans are EUR 5/month for 250 GB and EUR 15/month for 1 TB;
> on a paid plan nothing expires, and they add client collections with proofing, an encrypted
> personal vault, file request links, workspace members and custom domains.
> Files are encrypted at rest with per-file keys (AES-256-GCM); end-to-end encryption, where
> the key is derived in the browser and never sent to Yungle, is optional and free.
> Self-hosted on a single EU server, run on renewable energy.
> 
> Unusually for this category it has a documented public API, a command-line client and a
> Model Context Protocol server — all available on the free tier — so sending files can be a
> step in a pipeline rather than a website someone visits.

## Product

- [Pricing](https://yungle.co/pricing): Send big files free with no account. Paid plans add storage that never expires, client collections, a private vault and your own domain. Cancel anytime.
- [Security](https://yungle.co/security): Every file encrypted with its own key, servers in Germany, virus scanning, a vault only your passphrase opens, and optional end-to-end encrypted transfers.
- [Sustainability](https://yungle.co/sustainability): Yungle runs on hydropower in Germany, sells nothing about you, and gives a tenth of its profits to protect rainforest. What that means, and what it does not.
- [Features](https://yungle.co/features): Transfers, client collections with proofing, a private vault, file requests, your own domain, team workspaces and an API. Everything Yungle does, in one place.
- [Who it’s for](https://yungle.co/for): How photographers, agencies, law firms, accountants, developers and privacy-minded people use Yungle to send, deliver and keep their files in Europe.
- [Compare](https://yungle.co/compare): Side-by-side comparisons of Yungle with WeTransfer, Dropbox Transfer, Smash, Filemail, SwissTransfer, Google Drive and OneDrive, from their own documentation.

## Features

- [Send large files free — no account needed](https://yungle.co/features/transfers): Send up to 10 GB free, with no account and no ads. Uploads survive a dropped connection, and you see who downloaded your files and when.
- [Client collections with proofing and galleries](https://yungle.co/features/collections): Give clients one lasting place for their files, with folders, previews, favourites and comments. No account or app needed on their side. Nothing expires.
- [Encrypted vault for your most sensitive files](https://yungle.co/features/vault): A private vault locked with a passphrase that never leaves your browser. For passports, contracts and anything you cannot afford to share by accident.
- [Request files from clients with one upload link](https://yungle.co/features/file-requests): Send one link and let clients upload straight into the right folder, without signing up. Every upload is checked for viruses before it reaches you.
- [White-label file sharing on your own domain](https://yungle.co/features/branding): Deliver files at files.yourstudio.com with your logo, colours and cover — and client emails that come from you. Your clients never see our name.
- [Team file sharing in one shared workspace](https://yungle.co/features/teams): Invite colleagues into one workspace with shared collections, transfers, contacts and storage. Everyone sends from the same place; the vault stays personal.
- [Password-protected file sharing, virus-scanned](https://yungle.co/features/secure-sharing): Password-protect any link, revoke it in one click, see who downloaded what, and send end-to-end encrypted transfers free. Every file is scanned for viruses.
- [File transfer API, CLI and MCP server](https://yungle.co/features/api): Send big files from your code: a documented REST API with an OpenAPI 3.1 spec, a command-line client, and a read-only MCP server for your AI agents.

## Who it is for

- [File sharing for creatives and their clients](https://yungle.co/for/creatives): Deliver shoots, edits and design files to clients without expiring links. Proofing, your own branding and resumable uploads, hosted in Europe.
- [Secure file sharing for business, hosted in the EU](https://yungle.co/for/business): Send contracts, reports and client files from servers in Germany. Per-file encryption, a data processing agreement, team workspaces and your own domain.
- [File transfer for developers: API, CLI and MCP](https://yungle.co/for/developers): Send large files to real people from scripts, pipelines and AI agents. A documented REST API, a CLI and a read-only MCP server, on servers in Germany.
- [Private file sharing with no ads and no tracking](https://yungle.co/for/privacy): Send files without ads, trackers or an account. Always encrypted, hosted in Germany, with optional end-to-end encrypted transfers and a vault only you can open.
- [A European alternative to Google Drive and Dropbox](https://yungle.co/for/european-alternative): Move your file sharing to a European company with servers in Germany. Send, deliver and keep files without routing them through US big tech first.
- [File sharing for photographers: deliver and proof](https://yungle.co/for/photographers): Deliver shoots to clients in a gallery that doesn’t expire. Clients favourite and comment without an account, and the whole shoot downloads as one zip.
- [Send video files to clients, with review built in](https://yungle.co/for/video-production): Send cuts, rushes and masters to clients with resumable uploads, video previews in the browser, comments for feedback, and download receipts per person.
- [File sharing for designers and design studios](https://yungle.co/for/designers): Hand off brand assets, source files and PDFs in a branded collection your client can come back to. Previews, comments and a link that doesn’t expire.
- [Client file sharing for agencies, on your domain](https://yungle.co/for/agencies): Deliver campaigns and collect assets from clients under your own brand. Shared workspace, contacts, file requests and collections on your own domain.
- [Send music files and stems, with previews](https://yungle.co/for/musicians): Send stems, mixes and masters at full quality. Audio previews in the browser, feedback in comments, and uploads that resume if your connection drops.
- [Secure file sharing for law firms, hosted in the EU](https://yungle.co/for/legal): Exchange case files and evidence with clients from servers in Germany. Per-file encryption, password links, a data processing agreement and expiry you set.
- [Secure file sharing for accountants and bookkeepers](https://yungle.co/for/accountants): Collect receipts and statements from clients with one link, and send annual accounts back encrypted. Hosted in Germany, virus-scanned, with a published DPA.
- [Secure file transfer for healthcare practices](https://yungle.co/for/healthcare): Send scans, reports and referral files from servers in Germany. Encrypted per file, with password links, expiry control and opt-in end-to-end encryption.
- [Send large CAD and BIM files to clients](https://yungle.co/for/architects): Send drawing sets, BIM models and renders with folders intact. Resumable uploads, a project collection that stays live, and file requests for consultants.
- [File sharing for schools and universities](https://yungle.co/for/education): Collect coursework and share lecture recordings from servers in Germany. File requests for submissions, collections for course material, no ads or trackers.
- [File sharing for nonprofits, on renewable power](https://yungle.co/for/non-profits): Share reports, campaign media and volunteer uploads without ads or tracking. Hosted on renewable power in Germany, with a tenth of profits going to rainforest.
- [File transfer for the public sector, hosted in the EU](https://yungle.co/for/public-sector): Exchange large files with citizens and suppliers from servers in Germany. Per-file encryption, a published DPA, virus-scanned uploads and expiry you control.
- [File sharing for AI agents with a read-only MCP](https://yungle.co/for/ai-agents): Let an AI agent hand files to people and check what arrived. A REST API for sending and a read-only MCP server, so your assistant can look but never send.
- [Automated file transfer from CI and scripts](https://yungle.co/for/automation): Send build artifacts, exports and reports to people from CI, cron jobs and scripts. A CLI and REST API with resumable uploads and download receipts.

## Comparisons

- [WeTransfer alternative — Yungle vs WeTransfer](https://yungle.co/compare/wetransfer): Compare Yungle with WeTransfer: 10 GB free per transfer with no monthly cap, no ads, files that can stay put, and servers in Germany. Sourced and dated.
- [Dropbox Transfer alternative — Yungle vs Dropbox](https://yungle.co/compare/dropbox-transfer): Yungle vs Dropbox Transfer: 10 GB free per transfer without an account, links you control, and your files on servers in Germany rather than in the US.
- [Smash alternative — Yungle vs Smash](https://yungle.co/compare/smash): Yungle vs Smash: 10 GB per free transfer with no queue and no ads, files that can stay as long as you like, and delivery pages on your own domain.
- [Filemail alternative — Yungle vs Filemail](https://yungle.co/compare/filemail): Yungle vs Filemail: 10 GB free per transfer without signing up, free password links, and client collections and file requests on servers in Germany.
- [SwissTransfer alternative — Yungle vs SwissTransfer](https://yungle.co/compare/swisstransfer): Yungle vs SwissTransfer: both private and free. Yungle stores files in the EU, keeps them as long as you like on a subscription, and adds collections and an API.
- [Google Drive alternative for sending files — Yungle](https://yungle.co/compare/google-drive): Stop sharing client files from Google Drive. Yungle sends and delivers big files from servers in Germany, with expiring links, receipts and no Google account.
- [OneDrive alternative for sending files — Yungle](https://yungle.co/compare/onedrive): On OneDrive, link passwords and expiry dates need Microsoft 365. Yungle transfers expire on their own and take a password for free, on servers in Germany.

## Developer documentation

- [Yungle API](https://yungle.co/developers): Send file transfers, build client collections and sync contacts from your own code. A JSON API with a command-line client and an MCP server; transfers work on the free plan.
- [Quickstart](https://yungle.co/developers/quickstart): Send your first file through the Yungle API in five minutes: create a key, register a transfer, upload with tus, send it and read the download receipt.
- [Authentication](https://yungle.co/developers/authentication): How to authenticate with the Yungle API: bearer API keys, the six available scopes, and what each failure status means.
- [Uploading files](https://yungle.co/developers/uploads): How to upload to Yungle with resumable tus uploads — so a dropped connection continues from the last committed part instead of starting again.
- [Transfers](https://yungle.co/developers/transfers): Create a transfer, upload the files, send it, and read download receipts per recipient — all from the Yungle API.
- [Collections](https://yungle.co/developers/collections): Create collections, upload folders with their structure intact, and invite clients as guests, using the Yungle API.
- [Contacts](https://yungle.co/developers/contacts): Read and write the workspace address book through the Yungle API, to keep it in step with whatever system you already use.
- [Errors](https://yungle.co/developers/errors): Every error code the Yungle API returns, what status it carries, and which ones are worth retrying.
- [Rate and email limits](https://yungle.co/developers/limits): Request limits, daily ceilings and the outbound email budget on the Yungle API, and how to stay under them.
- [What the API cannot do](https://yungle.co/developers/unsupported): The limits of the Yungle API, separating deliberate omissions from what is genuinely impossible — including why the vault can never be reachable.
- [API changelog](https://yungle.co/developers/changelog): What changed in the Yungle API and when, plus the versioning policy: /api/v1 is additive-only.
- [CLI reference](https://yungle.co/developers/cli): Every yungle command and flag: send files from a terminal, push folders into collections, list and revoke transfers, and connect an AI assistant.
- [MCP server](https://yungle.co/developers/mcp): Connect Claude, Cursor or Windsurf to Yungle with the MCP server: the eleven tools, what each answers, how to install it, and why it cannot send.
- [Send CI build artefacts to a client](https://yungle.co/developers/recipes/ci-artefacts): A GitHub Actions workflow that uploads build artefacts to Yungle with the CLI and emails the link to a client, with the API key kept in a secret.
- [A nightly report hand-off](https://yungle.co/developers/recipes/nightly-report): Send a generated report every night from cron with yungle send --json, parse the link with jq, and keep a log of what went out and when.
- [Send files from Python](https://yungle.co/developers/recipes/python): A complete Python script that creates a Yungle transfer, uploads large files resumably with tus, sends it and checks the download receipts.
- [A collection per client](https://yungle.co/developers/recipes/client-collection): Create a collection for each client from a script, upload folders into it with their structure intact, and hand the client its secret link.
- [Agent hand-off over MCP](https://yungle.co/developers/recipes/agent-hand-off): Let an AI assistant answer questions about your transfers and collections through the Yungle MCP server — and what it deliberately cannot do.
- [Send large files from the command line](https://yungle.co/developers/guides/send-large-files-from-the-command-line): How to send large files from your terminal with a resumable upload that survives an interrupted connection or a closed laptop — no browser tab to keep open.
- [A WeTransfer alternative with an API](https://yungle.co/developers/guides/wetransfer-alternative-with-an-api): An EU-hosted file transfer service with a documented public API, a command-line client and per-file encryption — including where it is the wrong choice.
- [File transfer for AI agents](https://yungle.co/developers/guides/file-transfer-for-ai-agents): Give an AI assistant read access to your file deliveries over MCP: ask which are expiring or whether a client downloaded. Read-only by design, and free.

## Tools

- [API](https://yungle.co/dashboard/api): Make delivery a step in your pipeline, not a website you visit.
- [CLI](https://yungle.co/dashboard/cli): For the uploads a browser tab should never have been asked to do.
- [MCP](https://yungle.co/dashboard/mcp): Let your own AI assistant answer questions about your deliveries.
- [OpenAPI 3.1 specification](https://yungle.co/api/v1/openapi.json): the machine-readable contract for the API, generated from the server's own validation schemas.
- `npm install -g yungle-cli` — the command-line client.
- `npx -y yungle-mcp` — the Model Context Protocol server (read-only tools).

## Guides

### Alternatives & comparisons

- [WeTransfer alternatives, compared honestly](https://yungle.co/blog/wetransfer-alternatives): A straight comparison of the main WeTransfer alternatives — what each one limits, where it stores your files, and which is worth moving to for your kind of work.
- [Free WeTransfer alternatives that are actually free](https://yungle.co/blog/free-wetransfer-alternatives): Which free file transfer services have a genuinely usable free tier, what each one really limits, and where the catch is hidden once your files get large.
- [A WeTransfer alternative for business use](https://yungle.co/blog/wetransfer-alternative-for-business): What changes when file transfer stops being personal: data processing agreements, retention control, shared accounts, and who is liable when a link leaks.
- [Dropbox Transfer alternatives](https://yungle.co/blog/dropbox-transfer-alternatives): Dropbox Transfer is tied to a Dropbox plan and its own limits. Here is what else sends large files, and what you give up or gain by moving off it.
- [Smash alternatives for sending large files](https://yungle.co/blog/smash-alternatives): Smash queues free transfers over 2 GB and expires them inside 7 days. How the alternatives handle large files, what each really limits, and which to move to.
- [Filemail alternatives](https://yungle.co/blog/filemail-alternatives): Filemail sells speed and very large transfers. Here is where its alternatives are stronger — retention, storage location, client delivery — and where they are not.
- [SwissTransfer alternatives](https://yungle.co/blog/swisstransfer-alternatives): SwissTransfer is free, Swiss-hosted and generous with size. Here is what its alternatives add — longer retention, client galleries, an API — and who needs them.
- [WeTransfer vs Dropbox: which one for what](https://yungle.co/blog/wetransfer-vs-dropbox): One sends files and forgets them, the other stores and syncs them. Which you want depends on whether the file is a delivery or a document you keep working on.
- [WeTransfer vs Google Drive for sending files](https://yungle.co/blog/wetransfer-vs-google-drive): Google Drive shares files from your storage; WeTransfer hands over a copy. The difference decides who keeps access, who pays for it, and what happens later.
- [The best file sharing for photographers](https://yungle.co/blog/best-file-transfer-for-photographers): Delivering a shoot is not the same as sending a file. What photographers need — galleries, client selection, folder structure — and which services provide it.
- [The best file transfer for video editors](https://yungle.co/blog/best-file-transfer-for-video-editors): Hundreds of gigabytes, dropped connections and clients who need a preview before the final. What video work demands from a transfer service, and who delivers it.
- [File sharing for creative agencies](https://yungle.co/blog/best-file-sharing-for-agencies): What changes when several people send on behalf of one company: shared accounts, a processing agreement, retention you control, and links that survive staff leaving.
- [European file sharing services, compared](https://yungle.co/blog/best-eu-file-sharing-services): Which file transfer services are actually run and hosted in Europe, how to tell the difference from an EU data centre, and when that distinction matters legally.
- [The best secure file transfer services](https://yungle.co/blog/best-secure-file-transfer-services): “Secure” covers four different promises, and most services keep only some of them. How to read the claims, and which services hold up when you check.
- [Google Drive sharing limits: what stops you sending](https://yungle.co/blog/google-drive-sharing-limits): Drive holds files up to 5 TB, so size is rarely the problem. The limits that bite are links that never expire, no download receipts, and data processed worldwide.
- [OneDrive sharing limits: what you get without 365](https://yungle.co/blog/onedrive-sharing-limits): OneDrive shares files up to 250 GB, but passwords and expiry dates on links need Microsoft 365, and data may be processed in the US. What that means for sending.
- [Smash vs WeTransfer: which free tier suits you?](https://yungle.co/blog/smash-vs-wetransfer): WeTransfer's free plan counts 3 GB or 10 transfers across a rolling month; Smash sends 2 GB with priority and queues bigger files. Sourced, dated, with no prices.
- [SwissTransfer vs WeTransfer: a sourced comparison](https://yungle.co/blog/swisstransfer-vs-wetransfer): SwissTransfer sends 50 GB free with no account and keeps files up to 30 days; WeTransfer's free plan allows 3 GB or 10 transfers a month. Where each one wins.

### Sending files

- [How to send large files: every method that works](https://yungle.co/blog/how-to-send-large-files): Email limits, cloud links, transfer services, and physical drives — what each one can actually carry, what it costs, and how to pick between them for your file.
- [How to send large files by email](https://yungle.co/blog/how-to-send-large-files-via-email): Every mail provider caps attachments at around 25 MB. Here is why, what happens when you exceed it, and the four reliable ways to send the file anyway.
- [How to send large video files](https://yungle.co/blog/how-to-send-large-video-files): Video is the file type that breaks every limit. What to compress, what never to compress, and how to get a multi-gigabyte cut to a client without it failing.
- [How to send large files through Gmail](https://yungle.co/blog/how-to-send-large-files-through-gmail): Gmail stops at 25 MB and offers you Drive instead. What that actually does to your file, who can then reach it, and when you want something else entirely.
- [How to send large files on WhatsApp](https://yungle.co/blog/how-to-send-large-files-on-whatsapp): WhatsApp caps documents at 2 GB and re-compresses video you send as media. How to keep the original quality, and what to use when the file is bigger than the cap.
- [How to make a video file smaller to send](https://yungle.co/blog/how-to-make-a-video-file-smaller): Which settings actually shrink a video, which quietly ruin it, and how to tell before you send whether compressing is the right answer or the wrong one.
- [How to send 4K and RAW video to a client](https://yungle.co/blog/how-to-send-4k-and-raw-video): ProRes, camera RAW and long 4K cuts run to hundreds of gigabytes. How to hand them over intact, resume when the upload drops, and avoid re-encoding the master.
- [How to send RAW photos to a client](https://yungle.co/blog/how-to-send-raw-photos-to-a-client): A shoot is hundreds of files with a folder structure that means something. How to deliver RAW and edited images so the client gets them the way you organised them.
- [How to send large files from an iPhone](https://yungle.co/blog/how-to-send-large-files-from-iphone): Mail Drop, AirDrop, iCloud links and the browser all handle big files differently on iOS. Which to use for a video, a folder, or something going to an Android phone.
- [How to send a whole folder, structure intact](https://yungle.co/blog/how-to-send-a-folder-of-files): Zipping loses nothing but adds a step for the recipient; most services flatten your folders instead. How to send a directory tree so it arrives the way it left.
- [How to send large files securely](https://yungle.co/blog/how-to-send-large-files-securely): Passwords, expiry, encryption and link secrecy each protect against something different. Which ones you actually need, and the order to think about them in.
- [Your WeTransfer link expired. Now what?](https://yungle.co/blog/wetransfer-link-expired): Expired transfers cannot be reopened by the recipient or the sender. What you can still do to get the file, and how to stop it happening on the next delivery.
- [How big is a 4K video file?](https://yungle.co/blog/how-big-is-a-4k-video-file): Roughly what a minute of 4K costs you in gigabytes, across the codecs people actually shoot and edit in — and why the same footage varies by a factor of thirty.
- [How to share BIM models and CAD files with clients](https://yungle.co/blog/share-bim-models-with-clients): Stop attaching models. Send each issue as one link with its folders intact, collect consultants' models with an upload link, and see who downloaded what.
- [How to collect year-end documents from clients](https://yungle.co/blog/collect-year-end-documents-from-clients): Give every client one upload link that files their bank statements, invoices and payroll straight into their own folder. No attachments, no chasing, no account.
- [How to send stems and mixes to a mix engineer](https://yungle.co/blog/how-to-send-stems): Bounce every stem from bar one at the session's sample rate, name files so they sort, add a notes file, and send the folder as one link — never re-encoded to MP3.
- [How to get useful client feedback on video cuts](https://yungle.co/blog/client-feedback-on-video-cuts): Send a browser-friendly review copy, one version per link, and ask for notes as timecode plus change. Keep the master out of it until the cut is approved.
- [How to share large files with students](https://yungle.co/blog/share-large-files-with-students): One link per course holds the term's recordings, slides and datasets; a separate upload link per assignment collects coursework into one folder. No student accounts.
- [Branded file transfer: your domain, not ours](https://yungle.co/blog/branded-file-transfer): Clients should download from files.yourstudio.com with your logo, not from someone else's site. What proper white-labelling includes, and the questions to ask first.
- [How to send files without an account](https://yungle.co/blog/send-files-without-an-account): Upload on the home page, copy the link, send it: no sign-up for you or the recipient. What anonymous sending gives up, and the signs you have outgrown it.

### Privacy & compliance

- [GDPR-compliant file transfer: what it takes](https://yungle.co/blog/gdpr-compliant-file-transfer): Sending someone else’s personal data makes you responsible for it. What the GDPR actually requires of a file transfer, and what to check before you trust a service.
- [Is WeTransfer GDPR-compliant?](https://yungle.co/blog/is-wetransfer-gdpr-compliant): The short answer is that it can be, and that the harder question is whether your use of it is. What their own documentation says, and what it leaves to you.
- [Is Dropbox GDPR-compliant?](https://yungle.co/blog/is-dropbox-gdpr-compliant): Dropbox offers a processing agreement and EU storage on some plans. What that covers, what it does not, and the questions worth asking before you rely on it.
- [How to send confidential documents](https://yungle.co/blog/how-to-send-confidential-documents): Contracts, records and anything under a duty of confidence need more than a link. The controls that matter, in the order they actually reduce your risk.
- [Sending sensitive client data safely](https://yungle.co/blog/sending-sensitive-client-data): Health, legal and financial files carry obligations ordinary work does not. What changes in practice, and what to have in place before the first delivery.
- [The US CLOUD Act and your files](https://yungle.co/blog/us-cloud-act-and-your-files): Jurisdiction follows the company, not the server. Why an EU data centre run by a US provider is a different guarantee from an EU company, and when that matters.
- [What “end-to-end encrypted” really means](https://yungle.co/blog/what-end-to-end-encrypted-really-means): Most services calling themselves encrypted hold the keys. What the difference buys you, what it costs, and how to work out which kind you are actually being sold.
- [How long should you keep client files?](https://yungle.co/blog/how-long-to-keep-client-files): Retention is a privacy control, not a storage bill. How to pick a period you can defend, and why keeping everything forever is the riskiest option available.
- [How to send case bundles securely](https://yungle.co/blog/send-case-bundles-securely): Send bundles as a link, not attachments: a password sent separately, an expiry date and a receipt — and end-to-end encryption for the documents that need it.
- [How to password-protect a download link properly](https://yungle.co/blog/password-protect-a-download-link): Set the password when you create the link and send it by text or phone, never in the same email. Add an expiry date, and know when a password is not enough.
- [Expiring download links: why and how long](https://yungle.co/blog/expiring-download-links): Every link you send outside your organisation should stop working on a date you choose. How to pick the lifetime, and what belongs in a lasting collection instead.

### Green file transfer

- [Eco-friendly file sharing: how to choose](https://yungle.co/blog/eco-friendly-file-sharing): What actually determines the footprint of sending a file, which claims are meaningful, and how to pick a service on evidence rather than on a green logo.
- [Green WeTransfer alternatives](https://yungle.co/blog/green-wetransfer-alternatives): File transfer services that run on renewable power and delete what they no longer need. What each one publishes about its energy, and how to verify the claim.
- [Is cloud storage bad for the environment?](https://yungle.co/blog/is-cloud-storage-bad-for-the-environment): Data centres use real power, but the number that matters is how long your files sit there. Where the footprint actually comes from, with the arithmetic shown.
- [How to tell if a service is actually green](https://yungle.co/blog/how-to-tell-if-a-service-is-actually-green): Renewable-matched, carbon-offset and genuinely efficient are three different claims. The questions that separate them, and the answers a real one can give.
- [The carbon footprint of sending a file](https://yungle.co/blog/carbon-footprint-of-sending-a-file): Roughly what a transfer costs in energy, why storing it for a year costs far more than sending it, and how much of the published arithmetic to actually trust.
- [The greenest file is the one you deleted](https://yungle.co/blog/deleting-files-is-the-cheapest-carbon-saving): Most of what any company stores is never opened again. Why retention is the largest lever you control, and how to shorten it without losing anything you need.
- [Green IT questions that get real answers](https://yungle.co/blog/sustainable-software-for-procurement): A vendor sustainability form most suppliers can pass without changing anything. The questions to ask instead, and what a good answer to each looks like.

### For developers

- [Moving files from your own code: an API guide](https://yungle.co/blog/file-transfer-api): What an API-first delivery pipeline looks like end to end — create, upload, finalise, notify — and the decisions that are painful to change once you have built it.
- [Resumable uploads, and why they are hard](https://yungle.co/blog/resumable-file-uploads): A 100 GB upload will drop before it finishes. How resumable protocols work, why chunk size is not a free choice, and the bug that makes a client retry forever.
- [Large file uploads in the browser](https://yungle.co/blog/large-file-upload-javascript): Chunking, retries and aborts in the browser, plus the two folder-drop traps almost every implementation still has — one of which silently truncates at 100 files.
- [Sending build artifacts from CI](https://yungle.co/blog/send-large-files-from-ci): Getting a large build output from a CI job to a client or a colleague, with real workflow configuration and the failure modes worth handling before they bite.
- [Giving an AI agent access to files, safely](https://yungle.co/blog/mcp-file-server-for-ai-agents): An agent that can read your files can be steered by them. Why a file MCP server should expose no destructive tool at all, and what a safe one looks like.
- [How to send files from Python, with receipts](https://yungle.co/blog/send-files-from-python): Let the Yungle CLI move the bytes resumably, parse its JSON in Python, then use requests to check who downloaded the file. About twenty lines, no uploader to write.

## Legal

- [Privacy Policy](https://yungle.co/legal/privacy)
- [Terms of Service](https://yungle.co/legal/terms)
- [Data Processing Agreement](https://yungle.co/legal/dpa)

## Notes

- The vault and end-to-end encrypted transfers are not reachable through the API or the MCP server, and cannot be: their keys are derived in the user's browser and never sent to Yungle.
- The MCP server has no tool that sends, deletes, invites or revokes. It reads metadata only.
- There are no webhooks yet; clients poll for download receipts.
- Comparison pages state only what a competitor publishes about itself, carry no competitor prices, and are stamped with the date they were checked.