xplorer² is a file manager for people who need more context than one Windows Explorer folder at a time. Its main window can show two folders side by side, keep other locations in tabs and collect items from unrelated folders into virtual scrap containers. xplorer² still works with real files on disk, so its extra views do not remove the consequences of a copy, move or delete command.
Two folders visible
The active pane is the source for most commands and the inactive pane can become the natural destination. Copy To and Move To make that relationship explicit without a separate browse dialog. The darker inactive pane is easy to overlook, however, so clicking the intended source before a large operation prevents a move in the wrong direction.
Tabs keep more folders open, but only two folder panes remain visible at once. A locked tab can protect an important location from accidental navigation. Folder trees, address bars and filters still apply to the pane that currently has focus.
Scraps hold references
A scrap container brings files from several physical folders into one operational list. Adding an item does not relocate it; the container records where the real file lives. This is useful for a project assembled from documents, pictures and source files stored across several directories.
The distinction matters after a move or deletion. If the real file changes location, a saved scrap can no longer load it through the old reference. xplorer² can show a missing-item log, but that log does not restore the file. Removing an item from the scrap is different from deleting the actual item, so the command wording deserves attention.
Flatten a tree
Browse Flat loads the contents of a folder and its subfolders into a scrap view. The Path column preserves the origin while sorting or filtering across the whole collection. It can expose duplicate names, old files or one extension scattered through a deep hierarchy without opening every branch.
Copying a mixed flat selection into one ordinary destination can collapse the source hierarchy. Files from different folders then arrive together, and identical names can conflict. A transfer that must retain relative paths needs a synchronization or structured copy workflow rather than an ordinary paste into one folder.
Transfers have policy
xplorer² can queue file transfers, filter which items move and control overwrite behaviour. A backup-style rule can replace an older destination only when the source is newer. Silent choices save prompts, but they can also conceal a bad assumption about dates or duplicate names.
Large transfers should begin with a small representative set. The log records missing or failed items, which helps repair a partial copy. A finished job still needs a count or comparison because a skipped locked file can leave the destination incomplete while most files copied correctly.
Comparison needs structure
Dual panes suit a direct folder comparison. Scrap containers can compare collections from more complicated trees, but deep synchronization must match corresponding folders first. When the hierarchies differ, xplorer² can leave items in an undetermined state. Loose name matching ignores folder paths, yet it cannot safely drive the same synchronization action.
The safest pattern is to separate discovery from modification: gather and filter the candidates, inspect paths and duplicate names, then run the copy or delete command on a reviewed selection. xplorer² makes large file sets easier to see; it does not decide which copy is authoritative.
