A mixed folder is easier to navigate when similar files live together. You may not remember a particular image’s name, but you know it is an image. You may need a presentation without knowing whether it was saved as PPTX or ODP. File type sorting creates familiar categories that match those everyday questions rather than requiring you to remember exact extensions.
This guide explains how to use FileJuggler.online for that first layer of organization. The tool runs locally after you select a folder in a compatible browser. You preview the proposed structure before allowing the app to move anything.
Choose categories that help you find things
Categories combine related formats. Images includes common photo and graphic extensions, Videos groups common video formats, and Audio covers sound files. Office material is separated into Documents, PDFs, Spreadsheets, and Presentations. Other recognized groups include archives, fonts, ebooks, code, data, design files, and disk images.
The purpose is navigation, not a judgment about importance. A small text note can matter more than a large presentation. The organizer does not decide what should be kept or deleted based on its category. It creates a structure that makes your own review easier.
Know the limits of extension-based classification
The category map uses filename extensions. It does not inspect document text, decode images, or execute programs. A file called photo.jpg is treated as an image because of its suffix, even if its contents are damaged or mislabeled. That makes the classification predictable, but it should not be mistaken for content validation.
Some formats have more than one plausible role. CSV is commonly used as a spreadsheet even though it is plain text data. JSON is grouped as data rather than being mixed with every source code file. If a category does not suit your workflow, a custom extension rule can send that format to your own destination.
Select a useful folder scope
Start with a folder containing ordinary user files, such as Downloads or an export collection. Avoid beginning with an entire source repository, application installation, or system directory. Files in those structures often depend on their paths, so reorganizing them by type could break the project even when every move succeeds technically.
The browser picker controls access. Select the specific folder, review the permission prompt, and leave nested scanning disabled until you know whether subfolders belong in the cleanup. Default exclusions help keep common project metadata and dependency folders out of recursive scans, but your own folder knowledge is still essential.
Review the scan before choosing a preset
The scan reports how many readable files were found, how many folders were encountered, and the total readable size. It gathers metadata incrementally rather than loading every file into memory. Unreadable entries are reported and are not silently treated as successfully scanned files.
If the count is unexpectedly low, check extension exclusions and whether the files live in nested folders. If it is unexpectedly high, stop and narrow the scope. A clear starting set is more valuable than a fast cleanup of the wrong directory. Scanning and changing scan settings do not move files.
Preview the file type organization
Choose File type and generate a preview. Read several example destinations: a PNG should go to Images, a PDF to PDFs, and an MP4 to Videos. Search for files you recognize and compare the planned paths with the structure you expected. The preview is a dry run, so you can revise the choice without undoing anything.
Inspect Other as a normal part of the process. Unrecognized extensions may be specialist files that deserve their own rule, or they may be temporary files you prefer to leave alone. Do not rename extensions simply to force a category match. A custom name or extension condition can express the desired destination more honestly.
Decide what to do with nested context
When files are spread across project subfolders, their relative locations may carry useful meaning. Preserve relative subfolder structure retains that hierarchy beneath the new category. Without it, files are gathered more directly into each category, which can create name conflicts when different subfolders contain common names such as cover.png.
Use the preview to compare the full paths. Images/ProjectA/cover.png preserves project identity, while Images/cover.png is simpler for a single known collection. Neither structure is universally better. Choose according to how you expect to retrieve the files, and exclude folders whose layout should remain unchanged.
Add a specific rule before a general rule
A broad category is often enough for a first pass. Later, you may want invoices separate from other PDFs or screenshots separate from other images. In Custom Rules, combine an extension condition with a filename condition, then choose a destination such as Documents/Invoices or Images/Screenshots.
Specific rules should usually appear before general ones. Stop after this rule matches makes a narrow rule final for that file. If you allow several matching rules, review each planned action in order. Rules evaluate metadata rather than the words inside a document, so a generic filename like scan001.pdf cannot reliably reveal whether it is an invoice.
Keep name conflicts visible
Category sorting can bring files from different locations into one destination. Keep both protects existing names by creating a numbered alternative when needed. It does not deduplicate content, and a collision does not prove that the files are the same. The activity log records the actual destination used during execution.
Choose Skip existing when you want to examine collisions manually. Choose replacement only when you intentionally want the destination contents overwritten and accept that session undo cannot restore the previous version. For a general first cleanup, keeping both is usually the easiest policy to review afterward.
Apply changes and keep the session open
Once the preview looks correct, start organization. The app copies and verifies each destination before removing a source for a move. This uses local disk space and takes longer for large files. Pause and cancel act between files, allowing the active operation to reach a safe stopping point.
Read the results rather than relying only on a completion heading. Some files may have changed since scanning or become unavailable. Warnings explain cases such as a destination copy succeeding while source removal fails. Use session undo promptly if needed, then rescan before planning another run. Closing the tab ends the in-memory undo session.