PDF, JPG, and ZIP files often accumulate together because they arrive from different tasks but land in the same folder. Reports and receipts use PDF, camera exports and saved graphics use JPG, while downloads and project handoffs arrive as ZIP archives. Sorting these formats into separate folders makes the collection easier to scan without changing what any file contains.
FileJuggler.online can group files by exact extension in a compatible desktop browser. You select the local folder, preview the destination for each item, and approve the operation only after checking the plan. The workflow stays on your device and does not require you to upload documents to a conversion or storage service.
Choose exact extension sorting instead of broad categories
File-type categories answer a broad question: is this a document, image, archive, video, or another familiar kind of file? Exact-extension sorting answers a narrower question: is this PDF, JPG, ZIP, DOCX, PNG, or something else? Choose exact extensions when format is the most useful way to retrieve or process the collection later.
For example, PDF and DOCX are both documents, but you might send only PDFs to a review workflow. JPG and PNG are both images, yet transparent PNG assets may need separate handling. ZIP and 7Z are both archives, but another application may accept only ZIP. Extension folders make those distinctions visible without inspecting file contents.
Sorting never converts a file. A JPG moved into a JPG folder keeps the same encoding, metadata, and extension. A badly named or corrupted file is not repaired. The organizer uses the final filename suffix as a predictable metadata signal, so the preview remains understandable.
Select a folder and control nested scanning
Open the organizer on the homepage and choose the folder through the browser picker. Direct folder writing requires HTTPS and current desktop Chrome, Edge, or another compatible Chromium browser. The page can work only inside the scope you select; it cannot silently browse unrelated directories.
Leave nested scanning off when the target is a mixed top-level folder and existing subfolders already have meaning. Turn it on when PDF, JPG, and ZIP files are scattered through subdirectories that are also part of the cleanup. If you include nested content, decide whether to preserve each file's relative subfolder beneath the new extension folder.
Preserving relative structure can prevent two same-named files from different projects from landing in one flat destination. It can also create deeper paths than you want. Add exclusions for package folders, application data, source-control directories, or any location managed by another tool. Then scan to collect metadata; scanning itself does not write files.
Preview PDF, JPG, and ZIP destinations
Choose the Extension preset and generate a preview. A PDF might be planned for `PDF/report.pdf`, a JPG for `JPG/photo.jpg`, and a ZIP for `ZIP/project.zip`. Matching is case insensitive, so `REPORT.PDF` and `report.pdf` are both recognized as PDF files even though their original capitalization remains unchanged.
Search the preview for `.pdf`, `.jpg`, and `.zip`, then filter conflicts. Inspect a few typical files and the awkward cases: names with several dots, hidden files, extensionless items, and files whose destination already exists. Unknown suffixes receive their own extension-based destination or an extensionless category according to the preset, rather than being treated as one of the three common formats.
Nothing changes while you preview. If the folder names, relative paths, or scan scope look wrong, revise the settings and regenerate the plan. This dry-run separation is the safest moment to spot a mistaken assumption before any directories are created.
Understand compound extensions and misleading names
The extension preset uses the last suffix. A file called `backup.tar.gz` is grouped under GZ, because `.gz` is the final extension. If your workflow needs TAR.GZ as a distinct group, create a custom filename rule using Ends with and match the complete `.tar.gz` suffix. Place that specific rule before the broad extension rule.
Names can also be misleading. A file called `photo.jpg.zip` is a ZIP archive according to its final suffix, even though JPG appears earlier. A file named `invoice.pdf.download` is grouped under DOWNLOAD until the browser or another program finishes and renames it. The organizer does not open the file to guess what it was meant to be.
These limits are useful because they keep rules deterministic. You can see exactly which part of the name caused a match. If content validation matters, use an appropriate inspection tool first and organize only after filenames correctly represent the files.
Decide how to handle repeated filenames
Moving several files into a single extension folder can reveal name collisions. Two project folders may both contain `cover.jpg`, or multiple downloads may use `document.pdf`. Keep both is the default policy and chooses an available numbered destination. It protects existing files from silent replacement while keeping each incoming item.
Skip existing leaves the new operation undone when the target name is occupied. This can be useful when you intend to review duplicates manually. Replace existing overwrites the destination only after explicit acknowledgement. Because the previous destination bytes are not retained, replacement does not provide the same session-undo protection as an ordinary move, copy, or rename.
The preview detects existing destinations, but execution checks again. That second check matters if another program saves a PDF or image after the preview. Read the final activity log to learn which exact destination path was used.
Organize safely and verify the result
Approve the queue only after the preview matches your plan. Operations run one at a time. For moves, the organizer copies the file to its destination, verifies bytes in bounded chunks, and removes the source only after successful verification. A failed write or verification leaves the original in place. A failed source removal leaves both copies and records a warning.
Large ZIP archives and high-resolution images can take time and temporarily require extra disk space. Avoid disconnecting external storage or editing target files during the run. Pause and cancel work between operations, allowing the current file to finish before the queue stops.
When the run completes, inspect the PDF, JPG, and ZIP folders and compare the activity summary with the plan. If some items failed or were skipped, resolve the permission or collision issue and perform a fresh scan. Do not reuse an old preview after files have changed.
Build a custom rule for only three formats
If you want to organize only PDF, JPG, and ZIP while leaving every other file in place, use Custom Rules. Create one rule per extension or an OR group that matches any of the three. Assign each extension its own Move action and destination. Separate rules are often easier to understand because each has one clear folder.
You can narrow the rules further. Combine PDF with a filename containing `invoice`, limit JPG to a parent path, or match ZIP files over a size threshold. Use Stop after match if later general rules should not add another operation. Generate a new preview whenever rule order or conditions change.
Export the rule set if you want to repeat it later. The JSON contains rule definitions, not your files, folder handles, or previous scan. On the next session, select the appropriate local folder again and review a fresh plan.
Keep extension folders useful over time
An extension structure is most useful when exact formats matter. If you repeatedly browse several extension folders together, broader Documents, Images, and Archives categories may be simpler. You can switch presets at any time because the homepage contains the full organizer rather than separate duplicated tool pages.
Use an on-demand rhythm that matches how quickly files accumulate. A weekly Downloads cleanup may be enough, while a production export folder may benefit from a review at the end of each project. FileJuggler.online does not watch folders in the background after the page closes.
Keep independent backups of important material. Session undo checks that the destination remains unchanged and the original location is available, but it cannot reverse every external event or restore overwritten destination contents.