Copy.fail has emerged as a notable project documenting instances of problematic copywriting found across the web. The platform catalogs examples of confusing, misleading, or deceptive text used by websites and applications, ranging from dark patterns to poorly written instructions that confuse users. With 648 upvotes and 277 comments on Hacker News, the project has sparked meaningful debate about UX writing practices, corporate responsibility, and the role of public platforms in addressing poor communication.
What Copy.fail Documents
The platform collects screenshots and descriptions of problematic copy instances, organizing them by category and severity. Examples include unclear consent mechanisms, confusing cancellation processes, misleading calls-to-action, and contradictory or deceptive language designed to manipulate user behavior. The project appears designed to raise awareness about how companies use language strategically—sometimes unethically—to influence user decisions and obscure important information.
The Case for Accountability and Standards
Supporters of the Copy.fail initiative argue that public documentation of poor UX writing serves an important function. They contend that many companies deliberately use confusing language or dark patterns to increase friction in processes they want users to avoid, such as unsubscribing from services or accessing refund policies. By highlighting these practices, advocates suggest the platform creates accountability pressure and raises industry awareness about what constitutes ethical copywriting.
Proponents also argue that UX writing deserves the same scrutiny applied to visual design or product features. They note that clear, honest communication is a fundamental aspect of user experience and that poor copy directly harms user trust and satisfaction. From this perspective, documenting bad examples serves as a resource for designers and product teams to understand and avoid similar mistakes. The project potentially influences companies to audit their own copy and consider the impact of their language choices on user experience and trust.
Additionally, supporters view Copy.fail as contributing to a broader conversation about deceptive digital practices. They argue that visibility around these issues can drive regulatory attention and encourage industry self-regulation before formal legislation becomes necessary.
Concerns and Counterarguments
Critics raise several concerns about the Copy.fail approach. Some question whether publicly shaming companies, without context, represents a fair assessment of complex product decisions. They note that copy exists within specific constraints—legal requirements, localization challenges, A/B testing results, and competing business objectives. A single screenshot may not capture the full context of why particular language was chosen or whether alternatives were considered.
Others argue that the project conflates different categories of problems. There is meaningful distinction between genuinely deceptive dark patterns designed to manipulate users versus awkward phrasing, confusing interface text, or legitimate business practices that users simply find inconvenient. Lumping these together under
Discussion (0)