5 GB free storage. No credit card needed. Start free
Security

File versioning: recover overwrites and ransomware damage

Restore earlier file versions and deleted files in dosya.dev, understand retention limits, and prepare a recovery routine for mistakes or ransomware.

, Founder, dosya.dev team updated 11 min read

File versioning can recover an earlier state after an overwrite, a bad edit or ransomware damage, provided that version is still retained and accessible. In dosya.dev, right-click a live file, choose Version history, open Versions in the viewer’s inspector and select Restore beside the required entry. The restored contents become a new latest version.

That is useful recovery, with boundaries. Version history does not prevent an attack, preserve unlimited versions or guarantee that every damaged file has a clean predecessor. It works best alongside recoverable trash, a separate backup and a small restoration test you perform before something goes wrong.

What version history can recover

A file can remain in the correct folder while containing the wrong information. Someone may save an empty spreadsheet over the household budget, export a small image over a full-resolution original, or replace a client’s approved document with an unfinished draft.

Version history gives those earlier contents a separate place in the file’s record. Restoring an entry makes it current again without creating a differently named file elsewhere in the workspace. Older entries remain only while retention and count limits permit them.

The mechanism is useful for collaboration too. A project coordinator can compare the previous proposal with today’s revision before choosing which should be current. A family member can retrieve last month’s working document without guessing which of several final-final filenames is trustworthy.

It does not merge changes. Restoring the earlier proposal makes that older content current for the shared file; it does not combine it with today’s edits. Preserve a copy for comparison when both versions contain useful work.

Version history, trash, sync and backup do different jobs

ProtectionWhat it helps recoverWhat to check
Version historyEarlier contents of a live fileAge limits, version-count cap and available saved data
Deleted or trashAn item removed from its folderTrash retention and whether it was permanently deleted
SyncCurrent changes across connected foldersTransfer direction, deletion behavior and conflict handling
Separate backupA recoverable copy outside the same failureIsolation, freshness and a tested restoration method

These protections can work together. If a document was deleted, restore the item from Deleted first, then inspect its retained versions if the recovered current content is wrong. If a sync pair is still propagating unwanted changes, pause it before recovery.

A sync client may upload a malicious change just as it uploads an intentional edit. Deletion-capable modes may also carry removals to their other endpoint. The backup-versus-sync guide explains why having the same current state in two places does not, by itself, preserve an older good state.

Know the retention limits before you need them

Dosya applies both an age rule and a version-count rule. Under the current fair-use and retention policy:

ItemFreePaid plans
Older file versionsSeven-day retention windowNo age limit
Version countWorkspace cap; newest ten by defaultWorkspace cap; newest ten by default
Files in DeletedSeven daysThirty days

The newest version of a live file is retained. A workspace administrator can change the version-count setting, and stored versions count toward storage use. The version-history help guide describes the interaction between these limits.

“No age limit” does not mean every version is kept forever. With a ten-version cap, enough subsequent revisions can remove the older state you wanted even when it is recent. Conversely, a seldom-edited file on Free can lose an older version because its seven-day window expires.

Consider a shared budget corrected once a month versus a project file repeatedly overwritten during a busy afternoon. The first needs enough time to discover a quiet mistake; the second needs enough retained revisions to survive many changes. Plan around how files actually change and how long a problem might remain unnoticed.

Changing plans after cleanup cannot recreate data that has already been removed. Restoring a version also cannot recover a file that never successfully uploaded. Check the actual available history rather than treating the plan description as proof that a particular copy exists.

Restore an earlier version step by step

Use a known file and confirm the active workspace. You need access to the file, and restoring requires permission to upload or modify it. A locked file cannot have its versions restored through this workflow.

  1. Open Files and locate the live file.
  2. Right-click it and choose Version history. This opens the full file viewer.
  3. Open Inspector (i) if the inspector is closed. Its accessible label is Toggle inspector; on smaller screens it can appear as a sheet.
  4. Select Versions beside Details. Check the available version count.
  5. Compare version numbers, dates, times, sizes and uploader details where shown. The current entry is marked Latest.
  6. Select an older row to preview it when the format supports preview. Selection changes your preview, not the shared file.
  7. Choose Restore on the row you intend to make current. This performs the action directly; there is no additional confirmation dialog in this workflow.
  8. Wait for Restored, then inspect the refreshed list for the new Latest entry.
  9. Close and reopen the file, or download its current copy, and verify the contents.

For example, if v2 is current and you restore v1, the restored contents become v3. You can return to v2 by restoring that retained entry later, but each restore creates another version and remains subject to the count cap.

Coordinate this action when other people are editing the file. They need to know which version is now current. A restore is a shared content change, whereas selecting an older row for preview is only an inspection step.

Download an old copy without changing the live file

Sometimes you only need to compare a paragraph, retrieve a removed spreadsheet formula or preserve an earlier design. Downloading the historical entry avoids changing what teammates currently see.

The historical-download guide identifies a specific path:

  1. In Files, click the target row once to open its details panel.
  2. Find Versions in that panel and identify the required revision.
  3. Choose the download icon on that revision’s row.
  4. Save it under a distinct local name, such as budget-v2.xlsx.
  5. Compare its size and contents with the expected earlier file.

Do not substitute the full viewer’s header Download button. That button retrieves Latest, even when an older version is selected for preview. The per-row icon in the Files details panel is the supported visible path for historical bytes.

A full password lock can also block this historical-download path even after you unlocked the preview. If the copy is needed, an authorized manager must review and change the protection through the supported controls; ordinary download permission alone does not bypass it.

Downloading an old version does not restore it or create a new history entry. It creates a local copy that you must store appropriately, especially when the document contains personal or client information.

Add a replacement to the right history

When deliberately revising an existing file in the web app, right-click it and choose Upload new version. Select the replacement, follow progress in the upload dock and wait for completion before reopening history.

This explicitly targets the existing file. Uploading a separately named copy is not necessarily a revision of the original, even when the filenames look related. If history contains only one version, check whether the newer document became a separate file instead.

For a team deliverable, this can keep a clear revision chain around one file record. For personal records, it helps distinguish an updated document from a second independent scan. Verify the selected target before replacing it; a correct upload into the wrong record still creates a confusing history.

Restore a deleted file or folder

Use Deleted when the item is missing from its live folder. The deleted-file recovery guide follows this sequence:

  1. Open Files in the workspace where the deletion occurred.
  2. Select Deleted in the file sidebar. Expand the sidebar if its labels are hidden.
  3. Find the item, open its three-dot menu and choose Restore.
  4. If it was removed with a parent folder, restore the parent folder first.
  5. Wait for Restored, return to the live folder and open the recovered item.

Restoring a folder brings back the remaining items removed with that folder. Files deleted separately beforehand remain in Deleted until restored separately. Files already permanently removed do not return.

A restored folder can return to the workspace top level if its original parent is unavailable, or receive a numbered name if the destination already contains that name. Read the result message and inspect the actual destination.

Deleted items continue to count toward storage until permanently removed. Delete permanently is not a cleanup step to use during recovery: it ends the recoverable trash state.

Use version history carefully after ransomware

Ransomware can encrypt, rename or delete files, and an incident may also involve stolen data or compromised credentials. Restoring file contents addresses only part of that damage. A usable older version cannot undo disclosure of information an attacker already copied.

If ransomware is suspected, contain the incident before restoring into connected working folders. Isolate affected systems, involve your organization’s IT or incident-response lead when applicable, and use a known-clean recovery environment. CISA’s StopRansomware guide describes containment, evidence preservation and recovery planning.

For the Dosya recovery work itself:

  1. Stop affected sync activity and confirm which workspaces and folders may contain damaged changes.
  2. From a trusted environment, preserve available records and identify candidate versions from before the visible damage.
  3. Download and inspect a small set of historical copies before restoring them broadly.
  4. Confirm that the recovered documents open and contain the expected work.
  5. Restore only after the environment and access used for recovery are safe to use, then verify each recovered file.

Timestamps and file activity records can help establish when visible modifications occurred. They do not prove the exact beginning of an intrusion or establish that an older file is clean. Use them as evidence to investigate, not an automatic “restore to this time” guarantee.

The documented web workflow restores individual files. Do not assume it provides a whole-workspace rollback or a one-click recovery of thousands of items. For a large incident, establish the scope and recovery method with private support and the people handling the incident before making mass changes.

Version history is also not an immutable, isolated backup. An account compromise, destructive authorized action, exhausted retention or many replacement versions can affect what remains recoverable. Protect the account and keep an independently recoverable copy of important material.

Troubleshoot missing history and failed restores

Only Details is visible. Open the viewer’s inspector and select Versions. The Version history menu opens the viewer but does not necessarily select that tab for you.

The needed revision is missing. Confirm the file and workspace, check for a separately uploaded copy, and review whether the replacement completed. Age or count cleanup may already have removed the revision.

Restore fails. Check that the file is live, your role permits modification and the item is not locked. Reload the viewer. For a repeated failure, send private support the version number, approximate time and exact error.

A downloaded copy still contains today’s changes. Confirm that you used the historical row’s download icon in the Files details panel, rather than the full viewer’s header button.

A restored file changes again. Pause the relevant sync pair or coordinate with active editors. Recovery does not stop another authorized client from writing a new version afterward.

Practice recovery with an unimportant file

Create a small test document, upload it, then use Upload new version for a visibly different copy. Inspect both entries, download the older one and restore it. Finally, open the resulting latest version and confirm the expected contents.

Repeat a separate trash test with a disposable file. Record who can perform those actions and how long the history remains available. A household can use a sample shopping list; a business can use a clearly marked test document outside active client work.

Pair this routine with the 3-2-1 backup approach, a sensible choice of external and cloud copies, and the account controls covered in cloud-storage safety. Each covers a different failure.

Open your files in dosya.dev and test one harmless restoration now. Knowing the exact path, the available history and the verification step makes recovery a practiced operation instead of a guess made under pressure.

Frequently asked questions

What is file versioning in cloud storage?

File versioning keeps earlier states of a file when its contents change. In dosya.dev, you can inspect retained versions, download an older copy or restore one as a new latest version. Availability depends on retention, the workspace version-count cap and whether the saved data still exists.

How do I restore an earlier file version in dosya.dev?

In Files, right-click the file and choose Version history. Open the viewer's inspector, select Versions and inspect the older entries. Restore on the chosen row immediately makes those contents a new latest version. Reopen or download the current file to verify the result.

How long does dosya.dev keep file versions?

Free has a seven-day window for older versions. Paid plans have no age limit, but both are subject to the workspace's version-count cap, which defaults to the newest ten versions. Stored versions count toward storage. The current version is retained.

Can version history recover files after ransomware?

It can help when an intact version from before the damage is still retained and accessible. It does not prevent infection, guarantee recovery or undo stolen data. Contain the incident and secure the recovery environment before restoring; keep a separate backup for failures that also affect the account or history.

What is the difference between version history and Deleted?

Version history recovers older contents of a live file. Deleted recovers an item removed from its folder while it remains in trash. Dosya keeps trash for seven days on Free and thirty days on paid plans. Restore a deleted item before using its version history.

Can I download an older version without restoring it?

Yes. Click the file row in Files, find Versions in its details panel and use the download icon beside the required historical entry. Save it under a distinct local name. The full viewer's header Download retrieves Latest, even when an older version is selected for preview.