Type to Confirm

Type to Confirm is a high intensity friction pattern that requires the user to type a specific phrase or the exact name of the item they are about to destroy before the action button activates. The field listens for an exact match and only then does the button go from disabled to live. This is not a suggestion. It is a gate. The pattern exists to defeat autopilot behavior in high stakes situations by forcing the user to engage with the specific identity of what they are eliminating. It turns deletion into a conscious declaration instead of a reflexive tap. In the spectrum of friction shapes it sits at the heavy end because it demands cognitive effort and time that lighter options like modals or pauses do not. The best teams use it to show that they value the users data more than they value the illusion of total seamlessness.

It is not a generic confirmation step or a simple modal with an are you sure headline. It is not the password requirement some products hide behind cancellation flows to make leaving feel like a security breach. It is not a pattern that should be copied without understanding the stakes of the action it protects. Using Type to Confirm on reversible or low impact actions feels like the product is lecturing the user instead of helping them. It is not dark pattern material when the intent is to protect the user from regret but it becomes exactly that when the intent is to protect company metrics from user choice. The pattern demands careful calibration otherwise it stops feeling like respect and starts feeling like suspicion.

GitHub nailed the pattern with its repository deletion flow. Users must type the repository name exactly as written before the button lights up. The modal explains in blunt terms that this cannot be undone and lists the specific data that will disappear including issues pull requests and collaborators. Stripe uses the same approach for revoking live API keys where the cost of a mistake could be hours of customer downtime. Linear requires typing the workspace name for deletion because that single action removes every project and every integration tied to the team. In 2025 AWS expanded its use of the pattern to cover deletion of RDS instances that host production databases. Notion applies it only to workspace level deletion while allowing single page deletion with a lighter confirmation because pages can be recovered. Figma added it for deleting organization accounts after seeing teams accidentally remove client facing spaces. Cursor added it before an AI agent could run bulk file deletion across a project and listed the exact number of files and directories at risk. Vercel requires it before nuking a production deployment tied to a custom domain. These examples prove the pattern works best when the consequences are explained immediately before the typing begins and when the typed string is directly tied to the thing being deleted rather than a generic word. The implementation details matter. The field usually has a label that repeats the instruction in bold. Some products show the required text in a separate box for easy reference but the best ones force the user to read and internalize it. The teams that still rely on one tap deletion for critical actions in 2026 are losing users to tools that demonstrate more care.

Use Type to Confirm when the action cannot be undone and the potential loss includes money data or reputation that cannot be recovered. It belongs in irreversible actions account deletion money flows that cannot be reversed and sensitive data wipes. It scales with the size of the potential mistake and should only appear after the user has already chosen the action. Recall the six places where friction earns its keep. Type to Confirm is the correct material for the top of the irreversible column and the account deletion column. For money flows a double confirm or summary screen often suffices. For AI tool calls the diff review is the equivalent forcing function. The key is matching the friction shape to the risk level. The voxel framework spectrum shows six escalating shapes and Type to Confirm is the one with the most weight. Do not use it for archiving projects sending messages or any action with a built in undo window. Do not use it at the beginning of the user journey or in flows the user has not yet committed to. Do not use it so frequently that it loses its ability to command attention. The friction audit framework from the parent article provides the exact decision tree. Run every flow through those four questions and the pattern choice becomes obvious. When used in the right places with the right weight it transforms a tap and pray product into one that users trust with their most important work.

Type to Confirm proves that the most respectful thing a product can do is make it hard to do the wrong thing.