A free local Windows utility

VISINVOKE
Backup Utility

Your folders.
Your own drives.

Copy important files to storage you control. Keep reusable projects, choose when to run and see the results.

Illustration of local documents and photographs copied to a user-owned external drive and NAS
Free with your VISINVOKE accountOn-demand copying to your own storage

A practical extra copy

Keep the copying work organised.

Personal photographs, client files and ongoing projects deserve a clear route to a second location. Backup Utility brings the source, destinations, progress and recorded outcome into one local Windows workspace.

Know what you are copying

Name a project and select its source folder. Return to that saved setup for the next run rather than reconstructing a manual copying task every time.

Choose where it belongs

Associate one project with one or more enabled locations. Use storage already connected or accessible from your computer, without a separate cloud-storage subscription.

Start when it suits you

Run a project on demand and follow the current file, transferred bytes and results. It is a deliberate copying workflow, not an automatic background schedule.

See what happened

Review copied, updated, skipped and failed counts. Keep the report and check important files yourself; a copy-operation result is not checksum verification.

Illustration of one selected project folder copied to two separate user-owned drives

Make it reusable

One source. More than one destination.

Choose a folder, name the project and select your backup locations. Keep work, photographs and other collections in separate saved jobs.

The selected destinations receive a project folder with the original relative file layout. You can browse those copies with ordinary file tools.

From folder to recorded result

A clear job, from start to finish.

Bring the decisions into view before you begin, then follow the copying work and review its outcome.

01 · Choose a source

Use the native folder picker to select the folder for this project. Give it a meaningful name so its history and destination folder are easy to recognise.

02 · Select your locations

Pick one or more enabled backup locations. Confirm the intended path and whether the location is accessible, especially when connecting an external drive or mapped share.

03 · Review the exclusions

Exclude folders by name in Settings. Matching names are skipped at any depth, including built-in exclusions such as node_modules, .git and __pycache__.

04 · Run when you choose

Start the saved project. When confirmation is enabled, review the source and locations before agreeing to proceed. There is no automatic scheduler.

05 · Follow or cancel

Watch the current location, file and running counts. Cancel if needed. A stopped or interrupted job must be reviewed rather than assumed to be a complete backup.

06 · Review the outcome

Inspect location results, history and the text report. Look into errors or inaccessible folders and independently check the copied files that matter.

Purposeful tools, together

The details that make repeat work easier.

A saved project is only the beginning. Backup Utility keeps destinations, copying rules, progress and recorded results connected to the same job.

Projects with a clear purpose

Give each backup project a meaningful name, choose its source folder and select one or more enabled locations. Keep personal photographs, business documents and creative work in separate reusable jobs.

Storage you already own

Choose local drives, external drives, network locations, NAS or mapped drives, and custom folders. A destination must be accessible from your Windows computer when you run the job.

On-demand copying

Start a backup when you choose. New files are copied, existing files are updated when needed, and equal-length files are skipped when the source is not newer. This is a size-and-time comparison, not a checksum test.

Additive, not a deletion mirror

A file that exists only at the destination is left there. A later run can still overwrite a matching destination file with an updated source; this is not a version-history archive.

Recognisable folder structure

Files keep their relative folder layout under the named project folder at each destination. Browse the result with ordinary file tools rather than a proprietary archive viewer.

Folder-name exclusions

Leave out folders by name at any depth, using case-insensitive matching. Built-in exclusions include node_modules, .git and __pycache__; add your own exclusions in Settings.

Progress while the job runs

Follow the current file and location, transferred bytes and copied, updated, skipped and failed counts. Cancel a run if you need to stop, then inspect its recorded outcome.

Results for each location

See how each destination performed rather than treating a multi-drive job as one undifferentiated result. An unavailable location or a file-copy failure remains an issue to investigate.

History you can revisit

Recorded runs bring the project, time, duration, status and file counts together. Compare recent outcomes and decide what needs attention before the next backup.

Reports beyond the dashboard

Open a text report containing the run outcome and location details. Choose the report folder in Settings and keep a useful record of the copying work.

Use the equipment you choose

Local, external or accessible network storage.

Five location categories organise the destination you select. They describe your storage path, not a managed storage service or a guarantee that a disconnected device is reachable.

Local and external drives

Use a local drive or a connected external drive for a separate copy. A second folder on the same physical device does not protect against loss of that device.

Network and NAS locations

Choose an accessible network location or NAS / mapped drive. Its permissions and connectivity still depend on your Windows environment and storage setup.

Custom folders

Use a specific folder as a named location when that better fits your organisation. Each project keeps its own subfolder beneath the selected location root.

Availability before copying

Location status helps you notice an unavailable path. The run checks it again and records an unavailable destination as failed rather than claiming a copy reached it.

Understand repeat runs

Copy new files. Update changed ones. Leave destination-only files.

This is an additive backup workflow, not a deletion mirror and not a retained version archive. Knowing that difference helps you choose the right job for it.

New files are copied

A source file without a matching destination file is copied into the same relative position inside the project folder.

Existing files may be updated

A matching destination file is updated unless its length matches and the source is not newer. The update overwrites that destination copy; older contents are not kept as a separate version.

The skip rule is explicit

Equal length plus a source modification time no newer than the destination allows the file to be skipped. It is not a byte-for-byte or cryptographic comparison.

Extra destination files stay

Files that exist only at a destination are not deleted by a later run. Keep your own organisation policy for copies you no longer need.

Illustration of completed backup runs with an amber exception kept visible

A useful record

Know how the last job ended.

History brings the project, time, duration, outcome and file counts together. Location results help identify where a multi-destination run had an issue.

Open its text report for the copying details. These records explain the run; they are not proof that inaccessible folders were included or that every file is recoverable.

Choose it for the job it does

Straightforward copying, with clear boundaries.

Use Backup Utility as part of a considered file-protection plan. It keeps on-demand copying organised without implying that a successful run replaces independent checks or a wider recovery strategy.

On-demand, not unattended

There is no scheduler or automatic retention policy. Start the job yourself and use an additional approach when unattended backup is essential.

Browsable copies, not version history

Files retain their folder layout, but matching destination files can be overwritten. There is no built-in version manager or dedicated restore workflow.

Copy results, not checksum proof

Counts and reports describe copying work. Content-hash verification is not included, and inaccessible directories can be skipped during discovery.

Your storage, your protection

This utility does not encrypt backups or upload them to cloud storage. Manage storage permissions, encryption and independent recovery checks separately.

VISINVOKE means value. Quality. Ownership. Rewards.

Free with your account

Backup Utility has no separate purchase price. Sign in through VISINVOKE DCC and work in the dedicated Windows product window.

Keep control of destinations

Use the drives and accessible storage paths you choose. The copying workflow does not require a VISINVOKE cloud backup account.

A saved setup, a visible outcome

Reusable projects reduce repeated setup. Progress, location results, history and reports make the work easier to follow.

A focused part of your toolkit

Use File Converter, PDF Toolkit and the other local utilities for their own jobs. Each product has a focused page explaining its capabilities.

Quick answers

Know how it fits before you start.

Clear access, clear copying rules and honest operational limits.

Is Backup Utility free?

Yes. Backup Utility is included free with a VISINVOKE account. Create your account, obtain Desktop Command Centre through the account installer page, sign in on Windows and open Backup Utility. There is no separate utility purchase.

Where do my files go?

To the enabled destination locations you choose, in a folder named for the project. Locations can be local or external drives, accessible network folders, NAS or mapped drives, and custom folders. File copying runs through your Windows computer, not a VISINVOKE cloud-storage service.

What happens when I run the same project again?

New files are copied. Existing files are skipped if they have the same length and the source is not newer; otherwise they are updated. Files found only at the destination are not deleted. Updated destination files can be overwritten, so repeated runs do not create retained historical versions.

Does it run automatic schedules or retain old versions?

No. Runs are started on demand. Backup Utility does not provide a scheduler, retention rules or version management. Choose an appropriate additional backup approach if you need unattended or historical recovery.

Are copies verified with checksums?

No. File-copy outcomes, counts and reports show what the job did; they are not content-hash verification or proof that every file is recoverable. Inaccessible source directories can be skipped. Check important copied files independently rather than relying on a success label alone.

Can I restore, encrypt or upload backups here?

Backup Utility does not provide a dedicated restore workflow, backup encryption or cloud uploads. The copied folder structure is directly browsable, so files can be handled with ordinary file tools. Protect your storage separately and avoid treating this utility as complete disaster-recovery protection.

Illustration of a connected desktop workspace with local files and devices

Continue in VISINVOKE

Your storage. Your local workspace.

Create a free VISINVOKE account first. Get Desktop Command Centre from your account installer page, sign in on Windows and open Backup Utility.

Choose a source folder and your destinations, save the project and run it when you are ready.