This is proving to be more interesting than I initially thought.
Can we first agree that there are valid reasons why someone might want to clear the ‘Recent files’ list? Suggesting that completely different working methods would eliminate the need to do so is, sorry, a moot point.
I also don’t think instructions in the Russian language are a concern.
The instructions start with SQLite, an open-source relational database engine that has been part of macOS since 2005.
The commands used are standard SQL queries. They do nothing more than select all records with a path entry and delete only these records.
The command does not contact any hidden servers or perform any other unusual actions. It does successfully clear the Recent Files with one command for all MSO apps.
The alternative solution that @mpainesyd found reveals yet another oddity in MS Office.
We’re looking at Secure Bookmarks, but what are they, and why does deleting them also delete the recent files list? Has anybody tested this yet?
Claude says:
Secure Bookmarks records security-scoped bookmarks — a macOS sandboxing mechanism that allows sandboxed apps like Word to persistently access files and folders outside their sandbox container, even across app restarts.
What’s inside it:
Encoded references to files and folders that the user has previously granted Word access to (e.g., by opening or saving a file via a dialog)
The bookmarks are binary-encoded and opaque — they contain the file path, volume info, and security permissions, but aren’t human-readable as plain text
Timestamps and metadata about when access was granted
Why it exists:
macOS’s App Sandbox requires apps to “re-earn” access to files outside their container each session — unless a secure bookmark is saved. Word stores these bookmarks in this plist so it can silently re-access recently used documents without prompting you every time.
In practice, this means:
If you’ve ever opened a file from your Desktop, Downloads, or a network share in Word, a bookmark to that location is likely recorded here. Deleting this file forces Word to re-request access to those locations, which can sometimes fix permission-related bugs (e.g., Word complaining it can’t save to a location it previously could).
A typical entry in the PLIST file looks like this (anonymised and w/ minor syntax errors to allow posting this):
< key > file:///Users/ANON/Library/Containers/com.apple.mail/Data/Library/Mail%20Downloads/F80E78BE-E398-4940-ACCF-40F0ANOSNF6E/ANON_Drawings_Nov_2025.docx
<key>kBookmarkDataKey</key>
<data>
Ym9vazAEAAAAAAUQQAAAAGTTxBWimOzWakFVUIl0fvhBDq3I8ZCMdDgO4H5M
OKMxAAAAAAAAAAAAAAAAAAAAABADAAAEAAAAAwMAAAAIACgFAAAAAQEAAFVz
ZXJzAAAAAwAAAAEBAABtaG0ABwAAAAEBAABMaWJyYXJ5AAoAAAABAQAAQ29u
dGFpbmVycwAADgAAAAEBAABjb20uYXBwbGUubWFpbAAABAAAAAEBAABEYXRh
DgAAAAEBAABNYWlsIERvd25sb2FkcwAAJAAAAAEBAABGODBFNzhCRS1FMzk4
LTQ5NDAtQUNDRi00MEYwQ0IzQTdGNkUkAAAAAQEAAFNpZG1vdXRoX0RyYXdp
bmdzX05vdmVtYmVyXzIwMjUuZG9jeCgAAAABBgAAEAAAACAAAAAsAAAAPAAA
AFAAAABoAAAALAAAAHQAAACMAAAAuAAAAAgAAAAEAwAAL0MAAAAAAAAIAAAA
BAMAAFYfB ANONANONANONANONANONAAJAAAAAEBAAAyNDRCRjI0NS1CMTA0LTQ3
N0ItQUM5NC0zREUzNDIyNjU2NDgYAAAAAQIAAIEAAAABAAAA7xMAAAEAAAAA
AAAAAAAAAAEAAAABAQAALwAAAAAAAAABBQAALwAAAAEBAABOU1VSTEJvb2tt
YXJrUXVhcmFudGluZU1vdW50ZWROZXR3b3JrVm9sdW1lc0tleQDYAAAA/v//
/wEAAAAAAAAAEQAAAANONANONANONANONANONAAAAAABAQAAD0AQAA
AAAAAEAQAADkAQAAAAAAAAIgAADEAgAAAAAAAAUgAAAwAgAAAAAAABAgAABA
AgAAAAAAABEgAAB4AgAAAAAAABIgAABYAgAAAAAAABMgAABoAgAAAAAAACAg
AACkAgAAAAAAADAgAADQAgAAAAAAAAHAAAAUAgAAAAAAABHAAAAgAAAAAAAA
ABLAAAAkAgAAAAAAABDQAAAEAAAAAAAAANgCAIDQAgAAAAAAAA==
</data>
<key>kLastUsedDateKey</key>
<date>2025-12-23T12:37:27Z</date>
<key>kUUIDKey</key>
<string>19FE6F38-C342-47F4-A4AE-330B12E8CFD3</string>
There are almost 200 such entries, including documents I have received as email attachments years back or projects that I completed many years ago, many more than the recent files list.