Everything e2w drive does, described properly. If you want the short version, it's here.
Everything below exists today. What doesn't exist is at the bottom, under its own heading.
| Function | What it does |
|---|---|
| Multiple watched folders | Any number of folders, anywhere on the machine, backed up in place.
Each one gets a name on the drive, so Accounts\report.docx from two
different places stay two different files rather than overwriting each other. |
| Nested folder handling | Choosing a folder inside one you already back up is refused and tells you which one covers it. Choosing a folder that contains ones you already back up absorbs them instead of backing them up twice. |
| Removing a folder never deletes the backup | Stop backing something up and what's already on the drive stays there. A folder that's merely missing — an unplugged drive, an undocked laptop — is skipped rather than treated as empty. |
| Change detection plus full rescan | Live file-change events, plus a periodic full rescan, because those events get dropped under load and while the agent is stopped. |
| Settling | A file isn't uploaded until its size and timestamp stop moving and it opens for reading, so half-written files never go up. |
| Unchanged files cost nothing | Files are compared by content. Touching a file, or saving it with no changes, produces no new version and uploads nothing. |
| Rename and move | Recognised as a move. No re-upload, and no deletion recorded. |
| Editor save patterns | Word and Excel save by writing a temporary file, deleting the original and renaming over it. A vanished file is held briefly and the deletion cancelled if the same content reappears, so pressing Ctrl+S never looks like a delete. |
| Temporary files ignored | ~$ files, .tmp, .crdownload,
.partial, Thumbs.db, desktop.ini. |
| Pre-flight check | Before the first byte moves it measures the selection and tells you whether it fits, and roughly how long it will take. |
| Folders it refuses | Windows, Program Files, ProgramData, the temp folders and whole drives are refused outright. Desktop and Documents are allowed with a warning, because both are often redirected into another sync product. |
| Install | A single executable, installed per-user. No administrator rights, no prompt, and it appears in Installed apps with a working uninstall. |
| Right-click in Explorer | "Back up this folder with e2w drive" on any folder. It adds to the list rather than replacing it. |
| Pairing and revocation | The app signs in once with your email and password, then holds a machine credential rather than the password. Revoking a machine stops it backing up on its very next request. |
| Health reporting | Each machine reports its last scan, how much is queued and its last error. If one goes quiet for three days you get an email, once, and it clears itself when the machine comes back. |
| Function | What it does |
|---|---|
| Unlimited history | Every change appends a new version and nothing is ever overwritten. There is no cap and no expiry on how many are kept. |
| Browse and download any version | Open the version count on a file row. Any past version can be downloaded on its own. |
| Old versions come back renamed | An older copy arrives as report (v2).docx, not
report.docx. You open history because you're not sure which copy you
want, so two identically-named files is exactly the wrong outcome. |
| Verified end to end | Every file carries a checksum taken before it leaves your machine and checked on the way back, so "intact" is a fact rather than an assumption. |
| Function | What it does |
|---|---|
| Deletes are never destructive | Deleting hides the file and keeps every byte and every version. This is deliberate: ransomware deletes files, and an agent that faithfully passed that on would destroy your only copy. |
| 30-day undelete | A deleted file or folder sits in Recently deleted for 30 days. A deleted folder is one entry, not one per file. |
| Restore is precise | You get back the version that was live at the moment of deletion, and a restore will never write over newer content that has appeared at that path since. |
| Who and where | Each entry names the person and the machine it was deleted from. |
| Show deleted in place | Off by default. A folder tells you how many hidden deleted files it holds, so the toggle only appears where it would do something. |
| Permanent delete is a request | On a shared drive it marks the files, waits 48 hours, and destroys them after. Everyone who can see them is emailed, and anyone can press Stop — a brake that needs permission isn't a brake. On a one-person drive there's nobody to tell, so it happens on confirmation. |
| Objections | Anyone can object instead of stopping it. That holds the clock indefinitely, keeps a line of reason, and only the drive's owner can let it proceed. The person who objected is told when it does. |
| Bulk purge | Pick from the bin, or take the lot. The button reads back what it's about to destroy — count and size — and the confirmation is typed rather than clicked. Ten thousand files run as a background job, not while you wait. |
| Delete by tag | Delete everything carrying a tag in one action. It goes through the ordinary bin, so it obeys folder permissions and file locks and is undoable. |
| Files written again are skipped | If a file marked for permanent deletion has been written to since, it is left alone. The mark is a record of a decision, not a standing licence. |
| Function | What it does |
|---|---|
| Rewind a folder or the whole drive | Pick a moment. Files that changed go back to the version that was current then, files deleted after it are restored, and files created after it are moved to the bin. |
| Preview first, always | It works out what would happen and changes nothing. The button that does it stays hidden until you've seen that preview, and if the answer has moved in the meantime it refuses rather than doing something you didn't agree to. |
| Only the files that change are listed | Counts are always exact. In a folder of 20,000 files you see the three that matter, not a truncated list of everything. |
| Nothing is destroyed | Files removed by a rewind go through the ordinary bin with the usual 30 days, labelled as a rewind so nobody finds them later and blames themselves. Version history is untouched. |
| Safe to repeat, and undoable | Running the same rewind twice does nothing the second time, so an interrupted one is simply run again. The undo is another rewind, back to the moment just before the first. |
| Function | What it does |
|---|---|
| Lock binds everybody | A lock is a property of the file, not a personal reminder. Your colleague's lock stops your delete. |
| Blocks deleting and overwriting | A new version replacing a signed document is arguably worse than a delete, because undelete doesn't cover it — the old version survives but the file now says something different. |
| What it doesn't block | Reading, downloading, sharing, moving and renaming all still work. It is a catch against losing the contents, not a freeze. |
| The reason travels with it | "Sarah locked this on 14 Aug — signed, do not replace" shows on the file, and is repeated in every refusal, so whoever is deciding whether to release it doesn't have to go and find out why it's there. |
| Release and override | Whoever set it can release it, and so can an owner or admin. An override is recorded as a different kind of event from an ordinary release. |
| The backup agent obeys it too | Deleting a locked file on your PC does not remove it from the drive. The answer names every file that was kept back and who locked it. |
| Function | What it does |
|---|---|
| Tags are shared, not personal | YearEnd2026 is only worth anything if it means the same thing to the person who applied it and the colleague searching a month later. The drive has one vocabulary. It records who applied each tag without making it theirs. |
| Made by using them | There's no "create a tag" step. Type it and it exists. The hash is
optional and case doesn't matter, so #YearEnd2026 and
yearend2026 are one tag. |
| Filter and multi-tag search | Filtering replaces the file list rather than opening a second screen, and shows full paths, because the whole point is that the matches are scattered. Several tags match any by default, with an option to require all of them. |
| Results carry all their tags | Not just the ones you searched for. Searching one tag is how you notice half the results are also marked approved. |
| Colours | A colour belongs to the tag, so everybody on the drive sees it. The picker opens on whatever colour the tag already has. |
| Folder tags don't cascade | A tag on a folder is a tag on that folder. If it flowed down to the contents, moving a file would silently change its tags with nobody having touched anything. |
| Tagging is a change, not a view | Somebody with read-only access can't alter the vocabulary everybody else searches by. |
| Function | What it does |
|---|---|
| Link shares | Send a link to somebody with no account. Optional password, optional expiry date, optional limit on downloads. Any combination. |
| Revoke means revoke | Switching a link off stops it for everybody, immediately. The link you send is never a direct address for the file — every open is re-checked, which is what makes revoking, expiry and the download counter mean anything at all. |
| Looking isn't downloading | Opening a link to see what it is doesn't spend one of its downloads. Otherwise "download limit" would quietly mean "open limit". |
| Password guessing is capped | Per link, so trying from somewhere else doesn't reset it. |
| View-only | A view-only link renders the file in the browser and never hands over anything the recipient could save the direct address of. |
| Share with a named person | They get it in their own "Shared with me", without gaining sight of anything else on your drive. |
| File requests | A link that lets somebody upload into a folder without an account. They can create new files and do nothing else: they can't list the drive, can't overwrite anything already there, and a file arriving with a colliding name is given a free one rather than becoming version 2 of yours. |
| One screen for all of it | Everything you're sharing, from every drive you're on, on one list with the drive named on each row. Change the access level in place — same link, same password, same expiry — or revoke it there. |
| Function | What it does |
|---|---|
| People aren't drives | One login, any number of drives — personal, company, a client's — all open at once rather than one at a time. Each can be given its own name and colour, for you only. |
| Invitations | Invite by email. They set their own password from a single-use link that lasts seven days. Nobody at e2w and nobody at your company ever sees it. |
| Inviting an existing account is safe | If the address already has a working account, the invitation grants access and nothing else. It never creates a way into an account that already works. |
| Roles | Sub-admin, worker, or read-only, with what each can do written under the picker. Ownership is transferred deliberately and can't be taken by an invite. |
| Per-folder access | Make a folder read-only for one person while they work normally elsewhere. The most specific rule wins, so read-write on a folder with read-only on one folder inside it resolves the way you'd expect. Read-only means they can't change it — it doesn't hide it from them. |
| Removal is immediate | Taking somebody off a drive takes effect on their very next action, not whenever their session happens to end. |
| Password reset | A link that lasts an hour and works once. Using it signs that account out everywhere. |
| We never confirm who's a customer | Sign-up and password reset give the same answer whether or not the address has an account, so neither becomes a way of asking who our customers are. |
| Export everything | One file containing your whole drive, plus a list of every file with its size, date and checksum so you can verify years later that what you kept is what you were given. One unreadable file is recorded as such rather than silently missing. |
| Close the account | Free, always, and it erases everything. A shared drive is only erased if you're the last person on it; otherwise it passes to whoever is left, because one person's erasure isn't consent to destroy a colleague's work. |
| Function | What it does |
|---|---|
| Search | By file name, across every drive you're on at once. Punctuation is
treated as punctuation, so searching budget_2026 doesn't also return
budgetX2026. |
| Preview | PDFs, images and text open in the browser. The file type is decided from the name against a fixed list, and anything a browser could execute isn't on it. |
| Folder tree and recent files | Every drive as a root in one tree, so moving between a folder in one and a folder in another is one click. Plus the files you last worked on. |
| Upload | Drag and drop, including whole folders with their structure intact. Interrupted uploads retry rather than failing outright. |
| Marks and a work queue | Pin, flag, colour, priority, a note and a due date on any file or folder. Yours are private unless you share them. One queue across every drive you're on, ordered pinned first, then priority, then what's due — which no other service can do, because none of them keeps more than one drive open at a time. |
| Copy for AI | A plain-text summary of what's changed, what's flagged and what's overdue, ready to paste into whatever assistant you already use. It's metadata only — names, dates, sizes, your own notes. Never the contents of a file. |
| Space | A usage bar on the file list, a warning as you approach the limit, and a page that tells you what's safe and what happens next before you hit it. |
| Unusual-activity alert | A drive whose existing files are suddenly being rewritten far faster than that drive's own normal raises an alert by email. It's judged against your own history, so a first backup of forty thousand files is never mistaken for an attack, and a drive that legitimately rewrites the same files every day isn't accused every week. It raises an alarm and changes nothing else. |
| Function | What it does |
|---|---|
| Where it is | Your files are in the Netherlands. The list of them — names, sizes, dates and who you've shared with — is in the United Kingdom. |
| Nothing reads your files | Nothing in e2w drive opens a file to look inside it: not to index it, not to scan it, not to build a preview thumbnail. Nothing is sent to an AI model or used to train one. We don't claim we couldn't read them — encryption where only you hold the key is designed and not switched on yet, and we'd rather say so. |
| One drive can never see another | Every request is answered only for the drive you're entitled to, and that check is part of the query itself rather than a filter applied afterwards. A valid identifier for a file on somebody else's drive matches nothing. |
| Access is short-lived | The permission your browser gets to fetch a file lasts about a minute and covers that one file. Every issue of one is logged. |
| Audit trail | Sign-ins, shares created and opened, permission changes, deletions and restores, all recorded with who, what and when. |
| Deleted really is deleted | When you permanently delete something, or close your account, the stored copies go before the records of them do — so a failure part-way leaves paperwork without files rather than files without paperwork. |
The list we'd want to read if we were the ones evaluating it.
3 GB free, no card. It ends when the drive is full rather than on a set date, and nothing is deleted when it does.