Comprehensible input: the i+1 method, and how to actually get it

Comprehensible input is language you can understand that sits just above your current level. Stephen Krashen's Input Hypothesis calls that gap i+1: what you already know (i) plus one new step. The claim is that you pick up a language mostly by understanding messages, reading and listening to things you can almost follow, not by drilling grammar tables. It's a hypothesis, not a settled law, and serious researchers have pushed back on it. But the practical version holds up well: the surest way in is a lot of input you can nearly understand, every day, until "nearly" turns into "yes".

What comprehensible input actually is

Comprehensible input is any language you can understand that's slightly harder than what you can already handle. You catch the gist, and one or two new words or structures come along for the ride. Your brain picks them up from context without you sitting down to memorize them. Krashen's shorthand for that sweet spot is i+1: your current level plus one. Too far below and you learn nothing new; too far above (i+5) and it's noise you tune out.

For example, if you know "the dog is eating" in Spanish and you hear "the dog is eating quickly", you didn't know quickly, but the rest carried you, so the new word lands. Scale that up to a whole podcast episode, a graded reader, or a slow YouTube video where you follow 90% and stretch for the last 10%, and that's comprehensible input doing its job.

The honest part: i+1 is a hypothesis, and it has critics

Most comprehensible input pages go quiet here. Krashen's Input Hypothesis is exactly that, a hypothesis, and it drew real academic pushback. Merrill Swain's output hypothesis came out of Canadian French-immersion studies: students who'd had years of rich input still made basic errors when they spoke, so Swain argued you also need output, being pushed to produce language, to get accurate. Barry McLaughlin went after the theory itself, arguing that "i+1" can't really be measured (how do you pin down someone's exact "i"?) and so the hypothesis is hard to test or falsify.

None of that means input doesn't work. It means input alone, with no speaking and no attention to how the language is built, tends to leave people who understand a lot but freeze when they open their mouths. The useful reading: make input the engine, and add output and a bit of noticing on top.

Can you learn a language with only comprehensible input?

You can get a long way to understanding with input alone, and understanding is the wall most people never get over. But "only input" has a ceiling on speaking. If you never talk, you build a passive language: you follow the film, you read the sign, and then you stall at the counter because producing words is a separate skill you haven't trained. The people who go input-heavy and still speak well almost always start talking at some point, even if late. Input first, output soon after.

How to actually get comprehensible input

The purist version of CI is simple and hard: spend hundreds of hours understanding your language, mostly by listening and watching, at a level you can nearly follow. Resources people actually use:

The catch is the same for all of them: you have to put in the hours, and early on it's hard to find input that's genuinely at your level rather than too easy or too hard. That's the gap an app can help with.

Where an app fits, and where it doesn't

Be clear-eyed about this: an app can't replace hours of real listening and watching, and anyone selling comprehensible input in five minutes a day is selling you something. What software is genuinely good at is the vocabulary side of i+1. TangoLango builds sentences that are words you already know plus one new thing, in your language's own dialect, with native audio on every one, and it schedules each sentence to come back right before you'd forget it. So every card is comprehensible by design, and your ear trains on real speech one sentence at a time.

The honest pairing: use us for the i+1 vocabulary and ear training that makes the hard input followable, and get your hours from real listening and watching on top. That's also why the method here is listening-first and why we won't promise fluency. No app makes you fluent. It makes you the person who understands what was just said, which is where speaking starts. For a closer look at the apps, here's a comprehensible input app built from your real life. For a related mechanic, sentence mining is the manual cousin: you pull i+1 sentences out of things you're reading. And for one language end to end, see how to learn European Portuguese.

Comprehensible input by language

The CI resources that work are language-specific, so we run a separate dialect-pure track for each of the 24 languages we teach. Start with your language:

"Krashen got the big thing right: you understand your way into a language, you don't grammar your way in. Where people go wrong is treating i+1 as the whole plan. Get a mountain of input you can almost follow, yes, but start talking sooner than feels comfortable. Understanding is the hard half. It just isn't the only half."

Nick, founder of TangoLango

Frequently asked questions

What is a comprehensible input example?

Any language you understand that's one step past your level. If you can follow "the train is late" in your target language and you hear "the train is late again", you didn't know again, but the sentence carried you, so the word sticks. A whole podcast episode you follow 90% of, with the last 10% stretching you, is comprehensible input at scale. Video with visuals, graded readers, and slow learner podcasts are the usual sources.

What is the formula for comprehensible input?

Krashen writes it as i+1. The i is your current level in the language, and the +1 is one step beyond it: input that's mostly understandable with a little new material you can pick up from context. The point of the formula is the balance. Input at your exact level (i+0) teaches nothing new, and input far above it (i+5) is noise. You want the near-miss that your brain can still decode.

What is the comprehensible input method?

Spending most of your study time understanding messages in the language, mainly by listening and reading things you can nearly follow, instead of drilling grammar and conjugation tables. The idea, from Krashen's Input Hypothesis, is that acquisition happens when you understand input slightly above your level. In practice people run it as hundreds of hours of watchable, listenable input graded to their level, then add speaking practice on top so understanding turns into talking.

Can you learn a language just with comprehensible input?

You can reach strong understanding with input alone, and understanding is the part most learners never crack. But "just input" leaves speaking behind: producing language is a separate skill, and researchers like Merrill Swain argued that output practice is needed to speak accurately. So input gets you most of the way to following real speech, then a bit of speaking practice turns that passive knowledge into conversation. Input first, output soon after.

Is comprehensible input better than grammar study?

For most learners, most of the time, input does the heavier lifting: you can memorize every rule and still not follow a fast speaker, because understanding real speech is a listening skill you only build by listening. Grammar study helps as a light touch that lets you notice patterns in the input you're already getting. The mistake is doing grammar instead of input rather than alongside a lot of it.

Learn the Portuguese people actually speak here

Ten minutes a day, native audio, your own real-life sentences. Free for 7 days.

Start comprehensible input in your language, 10 minutes a day (free 7 days)