Quick Answer: WQ Files is a sideloaded iOS file browser that reads other apps' data containers, system containers, and App Groups without a jailbreak or kernel exploit. It uses the worse_query sandbox technique, runs on iOS 26 and iOS 27, and can back up, restore, and clear app data. Its tools include a plist editor, a hex editor, and a read-only SQLite viewer.
Most file managers on iPhone stop at your own Files folders. Sooner or later, you want to see what an app actually stored, why a cache ballooned to 4 GB, or what a configuration profile left behind. That's where a iOS file browser that can reach other containers gets interesting, and also where it gets risky. WQ Files is an open-source project by kolbicz, and it's worth understanding exactly what it does before you install it.
What WQ Files actually is
The name comes from worse_query, a sandbox technique documented by Taj C (forcequit) in the worse_query project. The WQ Files repository describes the app as a file browser, app data manager, and cache cleaner. It says it reaches other apps' and system containers with no jailbreak and no kernel exploit, and that it reimplements the worse_query approach.
The project is tested on iOS 26.7.1, 27.0.1, and 27.2. That range matters, because behavior differs sharply between versions. Here's where most people get tripped up: the same button can work on one iOS release and quietly do less on another.
iOS 26 and iOS 27 don't behave the same
The README lays out a clear split. On iOS 26 (26.0 to 26.7.2), support is preliminary. WQ Files hides System Data and System Groups, and the Cache Cleaner has no crash-log section. App, extension, daemon, and App Group containers are still reachable.
Here's the practical difference:
| Capability | iOS 26 (26.0–26.7.2) | iOS 27 |
|---|---|---|
| App Data and App Groups | Listed from the LaunchServices database, found once and remembered | Container parents are listable |
| System Data | Hidden | Listing only; contents owned by root |
| Full scan time | Would take most of an hour; avoided by using LaunchServices | Lower on the same data set |
| App icons | Placeholder symbol tiles only | Real icons from app bundles |
| Backup, restore, clear app data | Works | Works |
The part practitioners don't advertise is that the iOS 26 path avoids a full inode scan by reading the LaunchServices database instead. That's a workaround for a real performance limit, not a missing feature in the codebase, but it does mean you may see a different list than you'd expect.
Browsing files, plists, hex, and SQLite
Once you're inside a container, the file browser is the core. Files open in the tool that fits them, and Open As lets you switch when the default guess is wrong. Saving writes back in place, keeping the same inode, owner, and attributes. That's a deliberate choice: many editors replace the file with a new one, which can break apps that check file identity.
Three specialized viewers do most of the heavy lifting:
- Plist editor: browse dictionaries and arrays, edit values by type (switches for booleans, dates, hex for data), and save in the file's own format, binary or XML. Editing a preference that controls app behavior is where you'll find the most useful changes.
- Hex viewer and editor: reads any file size in pages, jumps to offsets, and overwrites bytes in place. Changed bytes stay highlighted until you save, and the file size never changes.
- SQLite viewer (read-only): lists tables and views with row counts, runs read-only queries, and exports CSV. It works on a copy of the database and its
-walfile, so the app's own data stays untouched. The README advises closing the app first to get an up-to-date copy. That's a useful detail: an open database may hold recent writes in the WAL that a copy taken mid-session won't reflect fully.
Here's where it gets interesting. The hex editor can change bytes, but the plist editor is the safer place to start for most people, because it validates the structure as you go.
Apps, backups, and the Cache Cleaner
The Apps screen lists each app with its data size. From there you can back up an app's Documents and Library, restore the latest backup, clear data, open the folder, or share a backup as a ZIP. The Cache Cleaner shows cache and temp size per app, with Select All, None, and Large Caches (50 MB and up) filters.
Most guides tell you to back up before clearing anything. The counter-intuitive part is that the Cache Cleaner and clear-data actions don't make a file-by-file backup at all. The README is explicit: those operations delete without one. Apps offers to back up Documents and Library first, but tmp is discarded and cannot be restored. If you clear an app's data without running that backup, there's no undo.
If you use the feature, follow this sequence:
- Close the target app completely, since backup, restore, and clear all assume it isn't running.
- Back up Documents and Library from the Apps screen and confirm the backup appears under App Backups.
- Only then clear data or clean caches.
That order matters because the README notes that App copies are verified by a source-stability digest, a destination-shape digest, and stored content hashes. Those checks protect against some failures, but they are not filesystem snapshots, so a target app that keeps running can still change data mid-copy.
Safety: what gets backed up, and what doesn't
Before WQ Files overwrites or deletes a regular file, it copies the original contents to Backups inside the app. Long-pressing a backup restores it to its original location. Backups are also reachable in the Files app, which is useful when something goes sideways.
The safety model has several sharp edges worth knowing:
- Old app backups are never pruned automatically. You'll need to delete them yourself, and the README calls this intentional so a safety copy is never discarded without a decision.
- In the file browser, only empty folders can be deleted. Symbolic links are removed as links.
- Locks are advisory. Another app that ignores them can still write at the same time.
- In-place writes are not crash-atomic. If power fails mid-save, the file can be left partially written.
- Generic overwrite or delete operations on backup storage are refused, to prevent recursive backups of backups. Valid backups can still be restored.
That said, the README is candid that real iOS signing, token issuance, power-loss behavior, and app-side concurrent writes still require validation on supported devices. Treat the safety features as meaningful protection, not a guarantee. Editing another app's or the system's files can break things, so keep the backups and change only what you understand.
Signing: why the App Group matters
WQ Files depends on an App Group entitlement. worse_query asks for access through your app's group container, so whatever signs the IPA has to provide one. The app uses whichever group it receives, so the name doesn't matter. The top of the Log screen shows the group it got, or "No App Group" if it got none.
Signing tools differ here. AltStore, SideStore, and Sideloadly with an Apple ID create the App Group automatically, which the README calls the easiest path. Certificate-based tools can fail if the provisioning profile is a wildcard profile (App ID *), because wildcard profiles can't contain an App Group. In that case, signing fails or the app reports "No App Group."
Keep in mind that this is a version-dependent technique. The README records that iOS 27.2 can't read the com.apple.containermanager.identifier attribute at all. Apple can change behavior between point releases, so a working setup today may not work after an update.
Troubleshooting the errors you'll actually see
Three messages cover most problems:
- Apps list is empty. This doesn't necessarily mean you have no apps. The Apps screen depends on a full
fsgetpathscan of the data volume, a technique credited to KAMUI by murk-sus. A denied parent or an exhausted scan bound may return only part of the list. The README says to check Log forenumerate:andapp scan:lines, then refresh instead of assuming the device is empty. NO TOKEN. The container path was visible, butwq_grantcouldn't obtain a sandbox token. Usual causes are a signer that dropped the App Group or a container the app-group query refuses.(no label). A token was obtained, but the container identifier couldn't be read. The folder stays browsable but can't be backed up or cleared until identity is available.
These messages are useful, because they tell you which layer failed. A missing token is a signing problem. A missing label is an identity problem. Neither is a reason to force operations.
Frequently Asked Questions
what is a iOS file browser that doesn't need a jailbreak?
A jailbreak-free iOS file browser reads files through sandbox access granted to the app itself, not through root access. WQ Files uses the worse_query technique and needs an App Group entitlement from its signer. It works on iOS 26 and iOS 27 with differences in what it can reach, and it cannot read the contents of System Data, which is root-owned.
how to back up an app's data before clearing it with WQ Files?
Close the target app, open Apps, and choose Back up Documents and Library. Confirm the backup appears under App Backups before clearing anything. The tmp folder is not included in backups and cannot be restored, so clear it only when you don't need its contents.
why does WQ Files show an empty app list?
An empty list usually means the scan returned only part of the data, not that no apps exist. Check the Log for enumerate: and app scan: messages, then refresh. The README notes that denied parents and scan-bound limits can return a partial subset.
is it safe to edit system files with an iOS file browser?
It's safe only to the extent you understand what you're changing and keep backups. WQ Files backs up regular files before overwriting or deleting them, but in-place writes aren't crash-atomic and locks are advisory. Editing system or other-app files can break things, so test changes on a device you can afford to reset.
Pick one app whose cache you're curious about, close it, back up its Documents and Library, and look at what's in its Caches folder. Then note what changed in the Log. Share this with anyone who wonders why their iPhone storage is full but nothing obvious is taking the space.