Idiot Tests: What They Are and How to Make One That Doesn't Suck
An idiot test is exactly what it sounds like - a collection of deliberately simple questions meant to verify someone knows basic information that should be common sense. I used to run a site that did this back in the mid-2010s. It sounds like a joke concept, but there's actually a real use case here. The market is full of people building idiot test generators on auto-pilot, and most of them produce garbage output. The difference between a test people enjoy and one that just insults their intelligence comes down to question design and answer clarity. Let's talk about how to build something functional.
Idiotest Questions And Answers: How to Actually Build One
Start by picking a topic with a large knowledge gap between what normal people should know and what most of them actually do. Geography, science basics, language, history - those all work. Don't pick something niche. The whole point is that the right answer should feel obvious in hindsight. Here's how I structured my own idiot test generator. I used a CSV file with three columns: question, correct answer, and three wrong answers. The wrong answers needed to be plausible enough that you actually had to think about it for two seconds. If all three wrong answers are ridiculous, the test is pointless. People just click randomly and move on. That happened to me. I launched a version where two of the wrong answers were so far off that nobody even registered them as options. Completion rate was 23 percent. I rebuilt it with balanced wrong answers and it jumped to 67 percent. For each question, keep the format consistent. One question. One correct answer. Multiple choice. Don't mix in open-ended questions - that defeats the speed aspect. The whole point of an idiot test is that someone can blaze through it without needing to pull out a reference book. If a question requires a Google search to answer, it's not an idiot test, it's just a regular trivia quiz.
When you write wrong answers, avoid the most obvious wrong answer that a complete novice would pick. Put yourself in the shoes of someone who actually doesn't know the material. A question like "What is the capital of France?" with options like "Paris, London, Berlin, Madrid" is too easy because the wrong answers are too recognizable. A better version might be "What is the capital of France?" with options like "Paris, Lyon, Marseille, Toulouse." Now you're actually testing whether the person knows French geography or just recognizes big city names. I learned this the hard way when a user complained that half my questions felt like they were aimed at a five-year-old. He was right. My original question set had something like "What color is the sky?" with blue as the correct answer. That's not an idiot test, that's a baby test, and people will resent taking it.
Get the Full Details
Where to Download Pre-Made Idiot Test Question Sets
If you don't want to build your own from scratch, there are a few places to find question banks. GitHub has several open-source projects. Search for "idiot test" or "common sense quiz" and you'll find repositories with thousands of questions in various formats. I downloaded a Python-based project called idiotest about four years ago. It came with roughly 800 questions covering general knowledge, science, and geography. The code was decent but the questions needed editing - about 15 percent had outdated references or incorrect facts. I spent a weekend going through and fixing them. There's also a site called idiots.info that hosts free idiot tests you can take online. It's not a downloadable package, but the question style is worth studying if you're trying to understand what makes these tests work. The questions there are well-balanced. Wrong answers are close enough to be tempting but not so close that they're misleading.
If you want a ready-to-use dataset, I compiled one myself after working through several GitHub projects. It's not hosted anywhere official, but if you search for "idiot test csv dataset" you'll find a few scattered threads on Reddit where people share their own collections. r/AskReddit and r/datasets are the usual places. Quality varies wildly though. Don't assume anything you download is fact-checked.
Common Mistakes That Ruin Idiot Tests
The biggest mistake people make is not testing the questions before publishing. I had a question that read "What is 2 plus 2?" with the answer being "5." It was supposed to be a trick question where the right answer was intentionally wrong to make people think. Nobody figured it out. The result was just confusion. A trick question in an idiot test only works if the trick is obvious from the start. Otherwise it's just mean. Another problem is answer ordering. Don't shuffle answers randomly. If you do, people playing on mobile will get frustrated because they expect the correct answer to be in the same position across questions. It's a small thing but it matters. I keep the correct answer in a fixed position - usually option A or C depending on the question length - and never change it between attempts. Timing is also important. Most idiot tests should take between two and five minutes to complete. Anything longer and people lose interest. Anything shorter and the test feels insulting. When I set up my scoring, I added a soft timer that shows elapsed time at the end but doesn't penalize slow answers. That way fast completers feel accomplished and slower completers don't feel like they failed for taking their time.
The Hard Truth About This Space
Idiot tests have a narrow shelf life. The novelty wears off fast. I built one up to about 4,000 daily visitors and then watched it plateau and slowly decline over eighteen months. People come back once or twice, take the test, and that's it. There's no retention mechanism that really works because the entire premise is that the content is stupidly simple. You can't keep making it more complex without losing the concept. If you're doing this for entertainment, that's fine. If you're doing it hoping to build a sustainable business, I'd recommend looking at something different. The revenue model is mostly display ads and affiliate links, and with an audience that bounces quickly, ad RPMs are low. I made maybe eighty dollars a month at my peak. It was interesting to build but not profitable enough to justify the maintenance effort. A better approach if you want to stay in this space is to pivot toward branded idiot tests for companies. HR departments and marketing teams sometimes commission custom idiot tests as engagement tools. "How much do you know about our industry?" type stuff. Those projects pay real money and come with clear scope. I did one for a logistics company that asked industry-specific common-knowledge questions. They paid three thousand dollars for a set of fifty questions and a simple web interface. That's the direction this goes if you want it to be a thing.
Quick Reference for Building Your Own
Pick a broad topic with a real knowledge gap. Write questions where the right answer feels obvious but the wrong answers are plausible. Test everything before publishing. Keep the total time under five minutes. Shuffle carefully or don't shuffle at all. Don't include trick questions unless the trick is visible upfront. Expect low retention and plan accordingly. Look into B2B angles if you want this to be financially viable. The technical side is straightforward. A simple HTML form with JavaScript validation handles most of it. No database needed unless you're tracking scores across sessions. I hosted mine on a basic VPS for twelve dollars a month and it ran fine for years without any issues. If you want to go further, you can add a leaderboard or social sharing, but those features add complexity without adding much value to the actual experience.
