Stop adding words to known upon lesson completion

Yeah, but that’s just not how LingQ is set up to work. It is intended as a learning software after all, and not just reading software. I mean, you “can” set it up to some extent to read long passages without triggering words to go into the “known” category, but like I said, it’s not really what LingQ is built to do. If you want to just read through pages of stuff without marking words, you should probably do it outside of LingQ, and just use LingQ when you have something you want to study.

There may come a time when LingQ does get an option to easily switch to the kind of free reading you prefer, but at the moment there is no easy option for that, as far as I know.

It works just fine for that, actually, other than this truly unfortunate UI/UX choice.

FWIW, I’m far from the first person to be frustrated with this and it’s been a long-standing complaint.

1 Like

It doesn’t work “fine” for that - after all, if it did, we wouldn’t be having this discussion.

It works “okay” for that “with certain settings enabled”, except (as you admit) for this issue, which is a big deal for you or we wouldn’t be here. The problem is, the feature you want is not fully implemented (presumably because the developers didn’t envisage a piece of learning software to be used merely as an e-reader), which is why you get that issue at the end of each lesson.

And the thing is, the developers may not be willing to make it more like an e-reader, partly because that’s not what LingQ was ever intended to be, and mostly because there’s a lot of pressure on them to serve the users more learning content. And I’m sure they feel that pressure to a great extent - one of the biggest criticisms of LingQ is that it doesn’t have enough languages and it doesn’t have enough content for the languages it does offer.

Linqg has a feature to import user content. I import content to learn from it, but sometimes it may contain words from other like French, or words in Cyrlic languages, or programming language source code. Assuming that it is ok to add ALL the “words” from the imported lesson is beyond my understanding. It is something that a lot of users complain about and it is not a rocket schience to implement.

Sorry, but you’re straight up wrong about that. I’ve run into this issue in sentence mode while actively learning a new lesson. i.e. using the software as intended.

Glad it works for you, though.

Interesting observation. That might be part of an unfortunate issue I have had with the Lingq dictionary for some time: Lingq dictionary Review - empty text in the "Select the missing word" activity - #4 by romanturovskyy.

Like I said, I don’t think it’s meant to be used the way you want to use it.

Could be part of the problem.

This is really a very very poor design choice. At a minimum, a question “Are you sure?” should be asked before setting everything to “known”.


The issue isn’t that we necessarily want to mark the lesson complete and leave blue words behind.

The issue is that it’s way too easy to unintentionally mark the lesson complete, which is then very, very painful to undo!


At a minimum, a question “Are you sure?” should be asked before setting everything to “known”.

I think there already is such a question on Android but not on Windows/Firefox.

It’s not that unusual to be paging through quickly when trying to find the place where you left off last time. It’s maddeningly easy to click “finish lesson” accidentally.

So I’m grateful for @roosterburton 's extensions. Auto-LingQ can turn all the blue words to yellow (status 1), which I like to do before starting a lesson. Then at least nothing will be automatically added to “known words.” But for those times when I forgot to do this and accidentally clicked the “finish lesson” button, there’s Rooster Observer to the rescue; there the status and definitions (etc.) for words can be viewed and adjusted as needed (and you can also see all the “known words.”)

jm2cw / ymmv / hth


This has been requested many times over the years, but @mark and the team are absolutely adamant that LingQ works this way. You need to use LingQ according to the LingQ method and the LingQ method is, to quote @zoran’s reply every time:

or let’s quote @zoran from the year before in August 2022:

or to quote @zoran from July 2020:

This is the LingQ method.


I can’t speak for others, but I’m not questioning the method. I’m expressing frustration at an awful UI/UX choice that really needs to be fixed. It should be moved or a confirmation added.

This UI/UX choice interferes with the method. That’s the whole complaint!

1 Like

I agree, but I also agree with Walkingpingu’s idea that maybe there should be an “Are You Sure” popup when we complete a lesson. I’m not usually a big fan of “Are you sure” popups (my attitude is that if I wasn’t sure, I wouldn’t have clicked the button), but in this case, I’m really getting kinda tired of having the same conversation on the forums every week with people who want to use LingQ as an e-reader.

1 Like

I was being sarcastic as a way to justify why LingQ has adamantly refused to change it for years.

I have been advocating for having an option to turn off ‘Complete lesson turns to Known’ for quite a while. Eg. this is from August 2022:

I almost rage quit LingQ last month because of this ‘feature’ LingQ refuses to change, when I accidentally clicked ‘Complete lesson’ and turned 200+ French and English words I didn’t click ‘ignore’ on to Known (while studying Italian).


It is worth mentioning that one of the benefits of using the “Paging moves to known” option is that it tracks your progress in the lesson and you don’t have to try to find the place you left off. It will take you to your last cleared page and won’t go any further if you use the handle in the progress bar.

With regard to moving words to known accidentally at the end if you have paging to known off, it’s easy enough to then just click on the words that you don’t know as you come across them and make LingQs for them instead. There is no real downside to adding words to known and then removing them from known again.

1 Like

Lingq can be a gorgeous e-reader. I’m unsure why creators are so strongly against using it as an e-reader. I use it kinda this way because it is much more effective to learn from your custom content in which you are interested (and this is what Linqg is about). I cannot find an alternative so far. Is there a better e-reader that tracks which words you marked as known and has an easy way to create an SRS learning dictionary? I like Lingq and hate it at the same time for these issues, but so far I like it more than hate :).

1 Like

This reminded me of a presentation I saw years ago.

With your product you “may see people who are not your intended customer use your product in unintended ways. This causes some people to panic. ‘My god the wrong people are buying our products in large quantities!’” - Guy Kawasaki, former Apple Chief SW Evangelist.

One reaction to this is to reject those customers, another is to embrace them. Given that LingQ could address this particular issue to satisfy both its “intended” users and these “unintended” users with what would effectively be an internal policy change, I don’t understand why they don’t just do it.


This is obviously an important issue and source of frustration for many of you in this thread, which is something we would like to do something about if possible. I will start by listing some observations after reading this thread:

  • We implemented this feature because it enables us to track users’ words properly. Our assumption is that users will click on any words they don’t know and this ability to page to known means you don’t have to individually move words to known which saves a lot of clicking over time.
  • Disabling this capability means a lot of unnecessary clicking making words known individually. This is directly opposed to one of our main goals which is to make reading on LingQ as efficient as possible. You need to learn tens of thousands of words. Forcing users to click on every one is not efficient.
  • Then, for those who wanted to be able to read the lesson first without dealing with words, we added the ability to turn off paging to known and do it at the end.
  • Paging to known allows users to track their progress through the lesson and effectively bookmark their last location.
  • Completing pages/lessons allows us to provide New Words and LingQs numbers for lessons as well as tracking an accurate Known Words number.
  • There is no harm in making LingQs that you feel you never need to learn. They won’t reoccur if they don’t matter and can be ignored in future.
  • Ignore words in other languages. This can be done as they appear or you can view the All Words tab in the Vocabulary list or in Sentence View if you View Vocabulary under the sentence.
  • If you come across words you don’t want to learn, Ignore them too.
  • On the iOS app the All Words view allows you to easily adjust the status of all including Known words up or down. We should enable this possibility on web too which would help when trying to move words back from known if you have completed the lesson by accident.
  • Our goal is to have users see their progress in their reading and stats. We track words as one of our main features. Disabling this for those users who want to use LingQ differently is perhaps possible but we don’t want users to do this before they realize the benefits of doing it the way we have designed the app. Making this an option, means that more people will do it and lose out on the benefits.

Other than the annoyance of accidentally clicking on Complete Lesson, what are some of the other reasons why you want to keep your lessons incomplete or uncleared? Fixing cleared words the odd time when I accidentally clear a page or sentence is mildly annoying but I read the page anyway and click on words I don’t know anyway. Sometimes these are words I have marked as known and other times they are words accidentally moved to known. It’s really not a big deal to me.
It is annoying when there are a lot of words to ignore in a text but if there are that many the All Words view helps a lot or sentence view. Better for me to click on all the words to ignore, than it is to have to click to add every known word forever.

Fundamentally, for the vast majority of our users who do read every word, why would you not deal with them all? You are reading them anyway so you are just trying to use a different classification system from ours.
Our system allows you to tell the system:

  • I want to learn this word 1-3.
  • I know this word
  • Foreign word/word I don’t want to learn - Ignore

Are you using blue for “I am not yet ready to learn this word”? We don’t believe this is a useful classification. We believe all words should be LingQed and the words that matter will reoccur and be learned over time.

This is a rambling post but I’m trying to lay out our point of view. Let me know your thoughts.


For users that have 25000+ known words, there are usually not so many words to add to known, so no unnecessary clicking. Please consider the experience for such users.

This is questionable. There are situations when I do want to learn a word as part of a phrase, but I don’t want to learn it in isolation, so leaving it as blue seems perfectly fine. I constantly use this.

Please consider a category of your users who already have a pretty high level of English and a ton of known words but still want to enjoy using LingQ to improve further.

In my example, I like LinhQ because of the following features. I read stuff (e.g., books) using an E-Ink reader or listen to videos on YouTube, and I import them into LingQ to quickly scan the content to find words I’ve never encountered. There are usually not a lot of such words, thus little clicking. I add known blue words to known and many other blue words as LingQs (dictionary) to learn them using the pretty good SRS dictionary. For me, having full control over which words I add to known is very important - allowing the system to accidentally add them as known can mess up my vocabulary because they will not be blue anymore, and thus, I will not be able to easily spot them next time without careful reading in the LingQ app itself.
I understand this might not be the main use case for the target audience, but it is a valid use case, and it almost works in LingQ; it is just a bit painful due to issues like auto-adding words. Making this use-case user-friendly might increase LingQ value for many users (for me, definitely). If this can be done be introducing a setting and it does not cost a lot - why not? Thanks for understanding.