TL;DR: A Redditor built a single prompt that turns ChatGPT into a careful Google Drive inventory clerk. It counts everything, flags duplicates and clutter, and waits for your yes before touching a single file.
A contributor going by u/TheLunarWhale posted this in r/ChatGPTPromptGenius, and it picked up 37 upvotes fast. The setup is simple: they use ChatGPT Plus with the Google Drive connector to clean up years of digital hoarding. No fancy app, no subscription tool. Just a long, careful prompt doing the work a human would dread.
Here’s the thing that makes this stand out. Most “clean my Drive” prompts tell the model to just go do it. This one builds a full inventory first, verifies its own work, and only then asks permission to act. That order matters more than it sounds.
Why This Prompt Actually Works
The author front-loads the boring part: enumeration. Before ChatGPT touches anything, it has to map the entire Drive folder by folder, starting at root, using high-limit folder listings instead of trusting the first response it gets back.
A few techniques worth noticing:
- Explicit skepticism: the prompt tells the model not to “treat a low-limit folder response as exhaustive.” That’s the author anticipating a real failure mode, where the AI stops early and calls it done.
- Cross-verification: it cross-checks typed searches against direct folder listings using Drive object IDs, not filenames. Two files named “Report.pdf” are not automatically the same file.
- Hard stop before destruction: step 3 says plainly, “Do not perform any destructive operation automatically.” Everything gets grouped into categories first, and nothing gets deleted without a yes from the human.
- Retry logic for flaky connectors: if a connector call fails despite working before, the prompt tells ChatGPT to retry in a fresh attempt before giving up. Small detail, but it saves you from a false “this isn’t possible” response.
This is role assignment plus constraint stacking. The model isn’t just asked to “organize my Drive.” It’s given a protocol, a reporting format, and a permission gate. That’s the difference between a prompt that sounds good and one that actually survives contact with 3,000 files.
What the Prompt Actually Does
Once the inventory finishes, ChatGPT reports totals for folders, files, and items. Then it breaks cleanup opportunities into clear buckets: exact duplicate names, near-duplicate names, empty folders, large files, old exports, obsolete archives, and temp files.
Nothing gets touched until you approve it. Once you do, ChatGPT keeps a running log of every delete, rename, move, and new folder it creates, plus whatever’s still left to review.
One detail readers should catch: the prompt draws a hard line between filename duplicates and confirmed content duplicates. Two files can share a name and be completely different documents. The author clearly got burned by that assumption before and wrote the fix straight into the prompt.
Use Cases
- Digital declutter after a big project: dump years of client folders, screenshots, and half-finished docs into a structured report before deciding what survives.
- Pre-migration audit: run this before moving to a new storage system, so you know exactly what you’re carrying over.
- Shared team drives: adapt it to flag stale exports and duplicate templates that pile up when five people are all saving to the same folder.
- Photo and export cleanup: the “old exports” and “large files” categories are especially useful if your Drive is full of design renders or video exports nobody deleted.
One commenter, u/mysterycly, said it was “actually helpful for someone like me who hasn’t cleaned my gdrive for awhile.” That’s the whole appeal here. This isn’t a novelty prompt. It’s a genuinely useful tool for a chore everyone avoids.
Prompt of the Day
Use the connected Google Drive tools.
Perform a complete cleanup and organization of my Google Drive.
First, perform a complete hierarchical inventory of My Drive using the validated Drive Enumeration Protocol.
Specifically:
- Begin explicitly at Google Drive root.
- Use high-ceiling list_folder enumeration (top_k=1000 or greater as necessary).
- Do not treat a low-limit folder response as exhaustive.
- Preserve Drive object IDs, parent IDs, exact displayed names, MIME/type information, and file/folder classification.
- Cross-check every directory using parent-scoped typed searches for folders, images, and documents.
- Follow every available typed-search page/continuation token to exhaustion.
- Reconcile typed-search results against direct folder listings using stable Drive object IDs.
- Preserve miscellaneous file types surfaced by list_folder even when typed search cannot represent them.
- Recursively enumerate every folder discovered beneath root.
- Restrict the inventory to the My Drive hierarchy. Do not include unrelated “Shared with me” objects.
- Preserve exact displayed names.
- Number every object.
- Clearly identify each object as a file or folder.
- Determine empty folders only through direct child enumeration.
- If any retrieval boundary prevents a defensible completeness determination, explicitly report the connector limitation instead of guessing.
After the inventory completes:
- Report total folders, total files, total items.
- Detect and report separately: exact duplicate displayed names, near-duplicate names, empty folders, large files, old exports, obsolete archives, temporary files, other obvious cleanup opportunities.
- Do not perform any destructive operation automatically.
- Group cleanup recommendations into categories: safe duplicate cleanup, archive cleanup, export cleanup, temporary files, organizational improvements, possible folder restructuring.
- Wait for my approval before every delete, rename, move, or other destructive operation.
- Once approved, use the Google Drive connector to perform only the approved operations, and keep a running log of deleted files, renamed files, moved files, created folders, and remaining recommendations.
- Never assume two files are identical merely because they share the same displayed filename. Report filename duplicates separately from confirmed content duplicates.
- If a connector operation unexpectedly fails despite previously validated behavior, retry the same operation in a fresh timeline before concluding the connector lacks the capability.
If your Drive connector isn’t turned on, this prompt won’t do you much good, and that’s a real tradeoff worth weighing before you flip it on. But if you’re already comfortable with connectors, this is one of the more responsible ways to use one: inventory first, permission gate before anything gets deleted.
Drop into the original thread on r/ChatGPTPromptGenius to see the full discussion and grab any follow-up prompts the author mentioned sharing.
Frequently Asked Questions
Q: Do you have a similar prompt for cleaning up Gmail?
The original poster mentioned having several similar prompts for Gmail cleanup and other organizing tasks, reach out via DM if you’re interested. While this specific prompt uses Google Drive connectors, you can adapt the same detailed enumeration approach for Gmail by substituting the drive tools for Gmail-specific commands like label organization and search filters.
Q: Will this work for Apple Files/Documents or other cloud storage?
This prompt is built specifically for Google Drive’s APIs, so it won’t work directly on iCloud, OneDrive, or Dropbox. That said, the same principle applies elsewhere: detailed inventory, hierarchy mapping, and organization. You’d just need to swap out the Google Drive commands for your platform’s equivalent tools.
Q: Should I be concerned about privacy when using Google Drive connectors?
The original poster was upfront about this, some people have valid privacy concerns about connecting ChatGPT to their Drive. Only use this if you’re comfortable with it. If you want to be cautious, you could move sensitive files to a separate folder first, or review OpenAI’s privacy policy to understand how your data is handled.
Using ChatGPT to help clean up Google Drive – a longer prompt
by u/TheLunarWhale in ChatGPTPromptGenius