Daniel's been building a home inventory system for years — warranties, spec sheets, photos, the works. And he's hit a problem that anyone who's ever tried to find a manual for a discontinued rice cooker will recognize instantly. For the top twenty percent of products — the big brands, the stuff Amazon sells by the truckload — PDFs are everywhere. Manufacturer sites, Amazon product pages, you're covered. But there's a long tail of products from smaller companies where the manual simply doesn't exist online. Daniel scans his own copies for his personal archive, and every time he does, he thinks: I should upload this so the next person can find it. But then the copyright question stops him cold. So today we're looking at who's already crowdsourcing this, what the legal landscape actually says, and whether Daniel should hit upload or hit delete.
The thing that makes this interesting is that it's not a technology problem. The scanning is trivial. The hosting is cheap. The obstacle is entirely legal — and it's a legal framework that was built for books and records and films, not for the instruction booklet that came with a hair dryer in 1994.
And the hair dryer company folded in 1997 and nobody knows who owns the rights to a twenty-page booklet about heat settings.
So let's start with what's actually out there. The projects that have tried to solve this.
And the different ways they've navigated the copyright question, because they're not all on the same footing.
The biggest one by volume is ManualsLib. They've got millions of manuals — everything from major appliances to obscure industrial equipment. And their legal posture is... well, it's honest about what they are. Their terms of service are explicit: you must own the copyright or have permission from the rights holder to upload anything. They're not claiming these manuals are public domain. They're not making a fair use argument. They're a hosting platform with a notice-and-takedown system under the DMCA.
And their takedown page is not a casual thing. I looked at it — it requires a physical signature, the specific URL of the infringing file, a statement under penalty of perjury. This is a formal legal process. They're not making it easy to issue a drive-by complaint.
Right. And that's the DMCA safe harbor at work. The platform isn't liable for what users upload, as long as they respond to valid takedown notices. But — and this is the part that matters for Daniel — the safe harbor protects ManualsLib. It does not protect the uploader.
So if a manufacturer sends a takedown notice, ManualsLib removes the file and they're in the clear. The person who uploaded it still infringed.
Still infringed. And copyright statutory damages are not a joke. Under section 504 of the Copyright Act, willful infringement can hit a hundred and fifty thousand dollars per work. Now, is a manufacturer going to sue an individual who uploaded a vacuum cleaner manual? Almost certainly not. The practical risk is low. But the legal exposure is real, and it's worth understanding what you're actually doing when you click upload.
The hundred and fifty thousand is the statutory maximum, not the likely outcome. But even the floor is meaningful.
The floor for non-willful infringement is seven hundred and fifty dollars per work. Still not nothing. And the thing about statutory damages is that they exist precisely because actual damages are hard to prove — the law doesn't require the rights holder to show they lost money. The infringement itself creates liability.
So ManualsLib is option one. What else is out there?
ManualsOnline is another aggregator — smaller, less comprehensive, but operating on a similar model. User uploads, DMCA compliance, terms that prohibit uploading copyrighted material without permission. Then there are the niche archives. ServiceManuals.net focuses on vintage electronics — old stereo equipment, ham radios, that kind of thing. These smaller sites often operate in a grayer zone because they're too small to attract attention, but their legal exposure is actually higher — they may not have the formal DMCA infrastructure that the big platforms maintain.
And then there's the Internet Archive, which is a different animal entirely.
Completely different. The Internet Archive's manual collection wasn't built by random users uploading PDFs. They scanned physical copies from library collections. So their legal footing relies on their status as a library and on fair use arguments — they're doing preservation work, they're a nonprofit, they're not competing with a commercial market for manuals.
Although that fair use argument took a serious hit recently.
The Hachette case. 2024. The publishers sued over the Internet Archive's controlled digital lending program for books, and the court ruled that scanning and lending entire books without a license was not fair use. The ruling narrowed the scope of what the Archive can do with copyrighted material, and even though that case was specifically about books, the reasoning affects everything they scan. If scanning a book for lending isn't fair use, scanning a manual for distribution is on even shakier ground.
Because a manual doesn't have the same cultural preservation argument that a book does. A court is going to look at a scanned novel and see a library doing library things. A scanned microwave manual? That's harder to fit into the fair use framework.
The four-factor fair use test doesn't care about cultural significance, though. It cares about the purpose and character of the use, the nature of the copyrighted work, the amount used, and the effect on the market. A manual actually scores reasonably well on some of those — it's factual rather than creative, which weighs in favor of fair use. The market harm is usually minimal because nobody is selling the manual. But you're reproducing the entire work, which weighs against you. And the purpose factor is tricky — preservation isn't one of the enumerated fair use purposes in the statute. Education, criticism, commentary, news reporting — those are the categories.
So the Internet Archive's manual collection is on a different legal footing than ManualsLib, but it's not bulletproof either.
Nothing in this space is bulletproof. And that brings us to the core legal problem: the long tail of orphaned documentation.
Let's define that. An orphan work is a copyrighted work whose owner can't be identified or located. The manual for a product from a company that dissolved in 2004 — the copyright still exists, but there's nobody to ask for permission.
And this is where the law and reality just completely diverge. For works made for hire — which covers almost all product manuals, since they're created by employees or contractors — copyright lasts ninety-five years from publication or a hundred and twenty years from creation, whichever is shorter.
So a manual published in 1995 is under copyright until 2090.
2090. The company that made the product hasn't existed for thirty years, the engineers are retired or dead, the brand was bought and sold twice and nobody knows who holds the IP — but the copyright is still valid for another sixty-four years. And there's no mechanism to clear it.
The US Copyright Office has been trying to fix this for decades.
They've proposed orphan works legislation multiple times. The most recent serious attempt was 2015 — the idea was to create a system where if you do a good-faith search for the rights holder and can't find them, you get limited liability if they later surface. You'd still have to pay reasonable compensation, but you wouldn't face statutory damages. It's a sensible compromise. It never passed.
What stopped it?
Photographers and visual artists lobbied hard against it. Their concern was that their work is especially easy to orphan — images get separated from attribution metadata all the time — and a liability shield for users of orphan works would effectively legalize widespread infringement of photography. The licensing market for stock photography is real money. Manuals don't have a licensing market, but the law doesn't distinguish.
So the orphan works problem for manuals is collateral damage from a fight about photography.
Pretty much. And that's been the state of things for a decade. No legislation, no regulatory fix, just a growing pile of manuals that are legally inaccessible and practically irreplaceable.
Okay, so let's talk about what this means for Daniel specifically. He scans a manual for a product from a company that no longer exists. He uploads it to ManualsLib. What's the actual risk?
The legal answer and the practical answer are different. Legally, he's infringing. The copyright is still valid, he doesn't have permission, and uploading a full reproduction to a public website is distribution — which is one of the exclusive rights the copyright holder has. The DMCA doesn't give him a defense; it gives the platform a defense.
And the practical answer?
The practical answer is that nobody is suing individuals for uploading old product manuals. I can't find a single case. The economics don't make sense — there are no damages to recover, the defendant is an individual with limited assets, and the PR would be terrible. A company that sued its own customers for helping other customers use its products? That's not a story any brand wants.
But the exposure exists, and Daniel's the kind of person who actually reads terms of service and worries about this stuff. That's the whole reason he asked.
Right. And there's a middle path. Before uploading anything, check whether the manufacturer has a published policy on manual reproduction. Some companies are explicit about it. Brother, for example — they make PDFs freely available on their site and don't restrict downloading or personal use. If a company has affirmatively made manuals available, uploading to an aggregator is less risky — not because the copyright is waived, but because the company's behavior suggests they won't enforce.
The problem is the companies that don't exist anymore. You can't check their policy. There's nobody to ask.
And that's the long tail. That's where the orphan works problem bites hardest. The very manuals that are most valuable to preserve — the ones for products where the manufacturer is gone and the documentation would otherwise be lost — are the ones with the least clear legal path.
There's a knock-on effect here that I think is worth naming. The copyright chill doesn't just affect Daniel. It affects the whole ecosystem. The people most likely to have rare manuals — hobbyists, repair technicians, people who buy storage units at auction — are also the most risk-averse about uploading. They're not lawyers. They hear "copyright infringement" and they stop. So the manuals that are hardest to find are the ones least likely to be shared. It's a negative feedback loop.
And the loss is real. I'm not being dramatic about this — product manuals contain information that you literally cannot get anywhere else. Torque specifications for a discontinued engine. The pinout diagram for a vintage synthesizer. The calibration procedure for a piece of lab equipment. When the manual is gone, that knowledge is gone.
Unless someone ignored the copyright risk and uploaded it anyway.
Which is exactly what happens. The entire crowdsourced manual ecosystem runs on people deciding the practical benefit outweighs the legal exposure. And I'm not sure that's wrong — but it's not a legal argument.
The right-to-repair movement intersects with this in an interesting way. As states pass right-to-repair laws, manufacturers are being compelled to provide documentation for current products. But those laws don't retroactively cover the long tail. So you've got a legal right to the manual for a 2026 product, but not for a 1996 product. The archive becomes de facto right-to-repair infrastructure — built on legally shaky ground.
One through legislation, one through civil disobedience. Neither one is fully adequate on its own.
The comparison to other crowdsourced documentation projects is instructive. Wikipedia uses fair use for images — they've got a detailed policy about when a copyrighted image can be used without permission, and it's tied to educational purpose and minimal use. Project Gutenberg focuses exclusively on public domain works — they do the copyright research before anything goes up. The manual aggregators are doing neither. They're not making a fair use case, and they're not limiting themselves to public domain. They're just... hosting and waiting for takedown notices.
Which is a functioning system, in practice. It's just not one that provides any legal comfort to the uploader.
Let's talk about what Daniel can actually do. If he wants to contribute to the commons without losing sleep, what's the path?
Step one: check for explicit permission. Some manufacturers have a page about manual distribution. Some have even released manuals under permissive terms. It's rare, but it's worth five minutes of searching.
Step two: if the company exists and there's no policy, he could ask. Send an email. The worst they can do is say no, and occasionally they say yes.
Step three: if the company doesn't exist, he's in orphan works territory. At that point, the options are to upload to a platform with a clear DMCA process — ManualsLib, for example — and accept the residual risk, or to keep the scan in his personal archive and not distribute it.
There's a fourth option that nobody talks about: donate the physical manual to a library. The Internet Archive accepts physical donations, and they have the institutional infrastructure to handle the copyright questions. It's slower, it's less satisfying than uploading a PDF and seeing it appear instantly, but it routes around the personal liability problem.
That's actually a great point. Libraries have different legal protections than individuals. If a library scans a manual for preservation purposes, section 108 of the Copyright Act gives them specific rights that don't apply to private citizens. It's still not a blanket permission, but it's a much stronger position.
And the library can make the scan available in ways that are legally defensible — controlled access, non-commercial use, tied to a specific research purpose.
The downside is that library-digitized manuals often end up behind access restrictions that make them harder to find than the wild-west aggregator sites. The Internet Archive's manual collection is searchable, but a lot of library-scanned materials are in institutional repositories that don't show up in Google.
So there's a tradeoff between accessibility and legality. The more accessible the manual, the more legally exposed the person who made it accessible.
That's the tension in one sentence. And it's not going away. The copyright term for works made for hire is fixed by statute — ninety-five years from publication. Congress could shorten it. Congress could create an orphan works exception. Congress has done neither, and there's no serious legislative effort underway right now.
What about the argument that manuals shouldn't be copyrightable at all? They're functional documents. Instructions. There's no creative expression in a torque specification.
The Copyright Office actually addressed this a long time ago. Blank forms and recipes are not copyrightable because they're purely functional — there's no creative expression. But a manual that includes explanatory text, diagrams, photographs — that crosses the threshold. The selection and arrangement of information involves creative choices. It's a low bar, and most manuals clear it.
Even the ones that are basically "insert tab A into slot B."
Even those. The diagram is a creative work. The wording of the instructions involves choices about clarity and sequence. Copyright protection is automatic and the threshold is minimal. You don't have to be writing literature.
So the law treats a microwave manual and a novel the same way. Same term. Same protections. Same penalties for infringement.
Formally, yes. In practice, nobody enforces manual copyrights the way publishers enforce book copyrights. But the law on the books doesn't distinguish.
Which brings us back to Daniel's original question. Should he upload?
If the manufacturer exists and has a permissive policy — yes, with minimal risk. If the manufacturer exists and has no policy — ask first, or accept the small but nonzero risk. If the manufacturer doesn't exist — the risk is lowest of all in practical terms, but the legal analysis is actually worse because there's no one to grant permission and the copyright is still valid.
The safest path, if he wants zero legal exposure, is to keep the scans in his personal system and not distribute them. Personal archiving — scanning a manual you own for your own use — is almost certainly fair use. It's the distribution that creates the legal issue.
Which is frustrating, because the whole point is helping other people find the manual. The personal scan solves Daniel's problem. The upload solves everyone else's.
And that's the tension Daniel's feeling. He's got a solution that works for him, and he wants to extend it to strangers on the internet, and the law says that's the part that gets you in trouble.
I think we need a perspective from someone who's actually been on the other side of this equation.
Go on.
Hilbert: Sony TA-E9000ES.
...The preamplifier?
Hilbert: Digital preamp. Nineteen ninety-eight. I worked for a small audio company in Connecticut that made a line of home theater processors. We sold maybe four thousand units total across three models. The company was called Meridian Audio Technologies — not the British Meridian, the Connecticut one that lasted six years and got bought by a holding company and dissolved.
Hilbert: I wrote the manuals. WordPerfect 6.1. Printed them on a LaserJet 4 in the back office. Spiral bound at Kinko's. There's a copyright notice on page two — copyright 1998 Meridian Audio Technologies, all rights reserved. That copyright is still valid. The company doesn't exist. The holding company that bought it was bought by another holding company. I tried to trace the IP once and gave up after three phone calls.
Hilbert: If someone scanned one of those manuals and uploaded it to ManualsLib, I'd be thrilled. Genuinely. I still have the original WordPerfect files on a Zip disk in a box. But legally, the copyright belongs to an entity that no longer functions and can't be reached. And the manual says all rights reserved. So the uploader is infringing. There's no question about it.
Do you want the manuals to be available?
Hilbert: Of course I do. I wrote them. They're good manuals. There's a section on room acoustics that I'm still proud of. But wanting it and having the legal right to authorize it are different things. I don't own the copyright. I was an employee. It was work for hire.
And you have no way to reach the rights holder.
Hilbert: The rights holder is a shell company inside a shell company. I don't even know if anyone at the parent entity knows they own a defunct audio brand's IP. If you called them and said "I'd like to scan your 1998 product manuals," they'd probably hang up.
Hilbert: This is the part that nobody talks about. Most of the people who created these manuals — the engineers, the technical writers — they want the documentation to survive. It's their work. They put effort into making it clear and useful. The idea that it's locked up for ninety-five years because of a legal framework that never contemplated this scenario — it's absurd. But it's also the law.
And the copyright notice on page two means it's not even an orphan work in the strict sense. You know who owns it. You just can't reach them.
Hilbert: Right. It's not that the owner is unknown. It's that the owner is unreachable and probably doesn't know they own it. That's a different category, and the proposed orphan works legislation wouldn't have covered it — the good-faith search requirement assumes the owner can be found. If you know the owner exists but can't get a response, you're still stuck.
That's a really important distinction. The orphan works problem is usually framed as "we don't know who owns this." But there's a whole category of works where we know exactly who owns them — a defunct entity, a dissolved corporation, an estate that doesn't answer letters — and there's still no path to permission.
Hilbert: I've got four of those processors in my basement. Two still work. The manuals are in a filing cabinet. I've thought about scanning them. I haven't, because I know the copyright situation and I don't want the headache. But if someone else did it, I wouldn't be upset.
That's the thing. The people who actually created the work want it preserved. The legal entity that owns it doesn't know it exists. And the law sides with the entity.
Hilbert: The law doesn't know the entity is a PO box in Delaware. It just knows there's a copyright and it hasn't expired.
What would you tell Daniel? Same situation, different product.
Hilbert: I'd tell him to check whether the company has a policy. If they do, follow it. If they don't, and the product is more than ten years old and the company is defunct — I'm not giving legal advice. I'm just saying I wouldn't lose sleep over it.
Hilbert: But I'd also tell him to keep good records. If you upload something, save a copy of the search you did to try to find the rights holder. Save the Wayback Machine link showing the company's website was down. If someone ever comes asking, you want to be able to show you made a good-faith effort. It's not a legal defense, but it's the kind of thing that makes a plaintiff less interested in pursuing you.
Documentation about documentation. Very on brand.
Hilbert: I'm serious. The practical risk management here is about making yourself an unattractive target. If a rights holder surfaces and sees that you tried to find them, and you're hosting a manual for a product they don't sell anymore, and you'll take it down immediately if they ask — most of them are going to send a takedown notice and move on. The statutory damages only come into play if they decide to sue, and they're not going to sue someone who's clearly acting in good faith over a twenty-year-old manual.
Unless the manual is for something that still has commercial value. Service manuals for current medical equipment, for example — that's a different risk profile entirely.
Hilbert: Completely different. I'm talking about consumer products. Toasters, VCRs, stereo equipment. The stuff where the only people looking for the manual are hobbyists and repair shops.
The line between consumer and commercial gets blurry fast, though. A manual for a discontinued lab centrifuge — is that consumer or commercial? The person looking for it is probably a researcher in a developing country who can't afford new equipment.
That's where the preservation argument is strongest and the legal path is weakest. The manual has enormous practical value to someone who needs it. The rights holder has no commercial interest in it. And the law provides no mechanism to bridge that gap.
If you take one thing from this episode, it's that the gap between what the law says and what makes sense for preservation is not an accident — it's a design feature. The copyright system was built for a world where publishing was expensive and distribution was controlled. It was never updated for a world where anyone can scan a document and make it available to everyone. And Congress has had multiple opportunities to fix the orphan works problem and hasn't done it.
The other piece I'd want people to remember is that the practical risk and the legal risk are different things, and Daniel's personal risk from uploading an old manual is low — but the systemic problem is real, and it means we're losing documentation that can't be replaced. The long tail stays long because the law makes it hard to shorten it.
The question I keep coming back to is whether copyright law should treat user manuals differently from creative works. The economic argument for manual copyright is weak. Nobody is buying a manual instead of a product. The manual exists to support the product, and when the product is discontinued and the company is gone, the manual serves no commercial purpose. But the law doesn't make that distinction, and changing it would require Congress to care about a problem that affects a tiny number of people.
Right-to-repair laws are chipping away at this from one direction. If manufacturers are required to provide documentation for current products, maybe eventually that requirement extends backward. But that's a long fight, and in the meantime, the archive depends on people who are willing to scan and upload despite the uncertainty.
Daniel's best practical path: check for explicit permission where possible, upload only to platforms with clear DMCA processes, and accept that the long tail will remain long for the foreseeable future. The manuals that are hardest to find will stay hard to find, not because the technology is difficult, but because the law hasn't caught up to the problem.
If you're sitting on a box of manuals for products from companies that don't exist anymore — you're holding something that has real value to someone, somewhere. The legal path to sharing it is messy. But the fact that you kept them at all is already more than most people did.
We should thank our producer Hilbert Flumingtop for keeping the show running, and for the Zip disk story.
If you've got a weird prompt you want us to dig into — copyright arcana, home inventory systems, or anything in between — email the show at show at my weird prompts dot com.
This has been My Weird Prompts. We'll be back soon.
