| Folder selection is not available on my phone | Some mobile browsers do not implement the directory selection interface used for scanning nested files. | Create a ZIP archive of the folder and upload that archive, or open the cleaner on a desktop browser with folder selection support. |
| The scan is marked partial | The tool capped duplicate hashing or another resource-heavy step to protect responsiveness on large selections. | Review the partial indicator and do not assume all duplicates were found. Select smaller subfolders or increase scan depth only within your device limits. |
| A necessary project file is marked as junk | File extension, path pattern, age or location can resemble a disposable cache even when a project still depends on the file. | Inspect its purpose, whitelist it and rerun the review. Keep active configurations, database files and unverified build dependencies. |
| The cleanup script does not delete any files | Exported scripts operate in dry-run mode by default, and may lack a correct base folder. | Read the script, set the exact authorized base directory, test printed paths and deliberately enable deletion only after backup and approval. |
| The script points to the wrong directory | The base path may not match the originally scanned folder or the folder was moved after export. | Do not execute the script. Correct and inspect the base path, verify every resolved target and regenerate the plan if anything is uncertain. |
| The clean-copy ZIP is missing some entries | Browser packaging can impose memory or size caps, with skipped files listed in the report. | Check skip warnings, split the input into smaller parts, and compare file counts before treating the archive as complete. |
| A ZIP file cannot be scanned | The ZIP may be damaged, encrypted, nonstandard or too large for the browser to unpack. | Verify the archive in a trusted extraction utility, provide an accessible unencrypted copy when authorized, or select the original folder instead. |
| The browser tab freezes or becomes unresponsive | Large directories, deep hashing or ZIP creation may exceed available CPU or memory. | Close unneeded tabs, scan a smaller subset, try Quick mode first and avoid packaging extremely large selections in one operation. |
| Scanning is much slower than expected | Large file counts, slow storage and content hashing can require substantial local work. | Begin with a narrow folder, use a less intensive scan mode and compare hashing coverage before requesting deeper analysis. |
| A binary file has no readable preview | The preview interface cannot show arbitrary binary formats as plain text. | Read the file metadata and open it with a suitable local application if you need to verify its contents. Do not remove it based only on an empty preview. |
| Duplicate files are not detected | The files may have different bytes, or their content was beyond the scan’s hashing cap. | Check whether the scan was partial and compare actual content. Use deeper hashing on smaller selections; do not expect near-duplicate photos to match. |
| Duplicate copies appear important | Identical files may sit in distinct backup sets, versioned releases or references required by another program. | Retain each copy with a valid purpose and document the keeper choice; do not use hash equality as automatic permission to delete. |
| Estimated savings are larger than actual free space gained | Some flagged files were retained, archive copies remained on disk, or filesystem accounting differs from raw file sizes. | Verify which source files were actually deleted, empty the appropriate trash only if intended, and measure real disk free space separately. |
| Storage estimate for this website looks too small | The browser storage API measures origin usage imperfectly and may omit detailed per-item sizes. | Treat the estimate as approximate and consult browser storage controls for further inspection. It is not a whole-device disk report. |
| Clearing browser storage signed me out | Site cookies or local data may hold preferences or session state. | Sign in again if required and restore saved preferences. Export important work before future site-storage clearing because deletion may not be reversible. |
| Other websites still have cached data | Same-origin security prevents this website from clearing another domain’s cookies, service workers or local storage. | Use your browser’s Settings to clear cache or site data for other domains, selecting the intended scope carefully. |
| PowerShell reports permissions or access denied | The executing account may lack access, files may be in use or a security rule may block the script. | Check ownership and app activity. Avoid unnecessary administrator elevation; seek authorized IT assistance instead of weakening safeguards. |
| Bash command fails on macOS or Linux | The shell, paths or script permissions may differ from the environment for which the file was prepared. | Review syntax and quoting, choose an appropriate shell and run the dry-run test with the correct base directory before changing any destructive setting. |
| The report is missing old files | The chosen date threshold, available timestamps or user-selected scope may exclude them. | Confirm that those paths were actually included, inspect timestamp accuracy and adjust the age cutoff conservatively. |
| The scanner flags a suspicious executable | Heuristic checks may treat certain executables and scripts as needing caution, without establishing that they are malicious. | Do not execute suspicious content. Check provenance and use a dedicated, updated antivirus or organizational security process. |