Overview of Files are over. All you need are URLs
This VergeCast episode centers on Paul Ford’s Tiny Little Office—a deliberately weird, surprisingly practical web app that puts documents, spreadsheets, and presentations directly into the URL itself. Host David Pierce and Ford use it as a jumping-off point to explore where software “lives” in the browser era, what privacy and ownership mean when the whole document is in a link, and how modern browser capabilities plus AI-assisted coding make it possible to build small, disposable, highly shareable software again.
The episode also includes a quick Verge news roundup, plus a strong end-of-show recommendation for the documentary You Can See Everything about Elizabeth Holmes.
Quick Verge news roundup
Before the main interview, the show hits a few tech headlines:
- Apple “Crackgate”: Some iPhone Duo owners are reporting inner-screen damage, allegedly linked to a hinge defect.
- Anthropic IPO filing: Anthropic has filed its S-1 with the SEC, signaling an eventual public offering.
- New iPad mini: Apple released a water-resistant iPad mini with a larger 8.5-inch OLED display, thinner/lighter design, and a $100 price increase.
- Touchscreen MacBook Pro rumors: The new iPad mini is framed as a warm-up to Apple’s rumored touchscreen MacBook Pro announcement.
Tiny Little Office: software inside a URL
What it is
Paul Ford describes Tiny Little Office as an office suite where the document data is embedded in the URL fragment rather than saved to a traditional server-backed file.
- The app can handle:
- word processing
- spreadsheets
- presentations
- outlining
- a few other small utility tools
- The data in the URL is:
- compressed
- human-unfriendly
- not meant to be edited manually
- optionally encrypted
How it works
- The part of the URL after the # stays in the browser and is not sent to the server by default.
- The browser loads the app’s JavaScript, interprets that fragment, and reconstructs the document locally.
- That means sharing the URL is effectively sharing the entire document.
- It can even be turned into a QR code, making the QR code itself the document container.
Why it’s unusual
Ford and Pierce emphasize that this inverts the normal model of software:
- no file sitting on a server
- no traditional account/database ownership model
- no big cloud doc to manage
- no permanent storage unless you opt into browser-saving modes
In other words, the software is designed to be lightweight, ephemeral, and disposable.
Big ideas and themes
Where does the computer live?
A recurring theme of the conversation is the question: Where is the computer now?
The episode frames Tiny Little Office as a thought experiment about:
- whether your data lives on your device
- in the browser
- on a remote server
- or in a link you pass around
It’s less about “the cloud” and more about moving computation and state into the browser and the URL bar itself.
Privacy, ownership, and ephemerality
Ford argues the system changes the meaning of ownership:
- if someone has the link, they effectively have the document
- if the link is deleted, the content can disappear
- if you share it in a chat, it can function like a temporary conversation artifact
This makes it especially well-suited for:
- group chats
- ephemeral brainstorming
- quick private sharing
- short-lived presentation decks
- “document-shaped messages” that shouldn’t live forever
A critique of modern productivity software
The conversation also touches on why tools like Google Drive can feel like a mess:
- too much clutter
- too much permanence
- too many stored artifacts
- too much “management” instead of actual use
Tiny Little Office is presented as a kind of antidote: make something, share it, let it vanish.
AI and browser maturity changed the cost curve
Ford says the project was possible because:
- browsers are now much more powerful and reliable
- encryption and networking APIs are mature
- AI-assisted coding made building the app dramatically faster
What once would have been too expensive or time-consuming to build for a joke or experiment is now cheap enough to try.
What Tiny Little Office is for
Ford is explicit that this is not meant to replace traditional office software for long-term work.
It’s better for:
- temporary collaboration
- text-heavy ideas
- chat-native workflows
- quick decks or docs you don’t want lingering forever
- “light privacy” use cases
It’s not ideal for:
- image-heavy documents
- large files
- traditional file management
- long-term archival work
Product philosophy and future plans
Ford says the project will stay transparent and open:
- open source / public-facing
- no hidden monetization tricks
- no dark patterns
- no secret server-side behavior
He also notes:
- there are already forks
- he’d love others to build on the idea
- v2 improvements could include better navigation, smaller links, and cleaner diagram handling
- the code may be useful as a baseline library for embedding word-processing/spreadsheet-like tools into other software
Host recommendation: You Can See Everything
In the closing segment, David Pierce strongly recommends seeing You Can See Everything, a documentary by Nathan Fielder and Lance Oppenheim about Elizabeth Holmes.
His main points:
- it’s fascinating even if you already know the story
- it’s especially powerful in a theater
- watching it with a crowd adds to the emotional and comedic impact
- it’s one of the most interesting tech-adjacent films he’s seen in a long time
Main takeaways
- URLs can be more than addresses: they can store full documents.
- Browser-native apps are getting powerful enough to host serious functionality without heavy backend infrastructure.
- Small, ephemeral software has real use cases, especially in chat-centric work.
- Ownership becomes fluid when the link is the document.
- Modern tooling and AI lower the cost of building weird, experimental software.
- The episode is ultimately about a bigger question: what happens to software when the web becomes the storage layer?