The workarounds for this are so straightforward that it’s unlikely you really need this added to the app.
First, if you don’t want to type on either platform, the simplest solution is to stop using the type-answer functionality in your card templates.
But if you want to type sometimes on desktop, you can leave your card templates as they are. Then, when you don’t want to type an answer, just don’t type. Ignore the type answer field and just proceed through studying the card.
The reasoning for having a switch to disable the feature on the mobile apps has to do with the intrusiveness of the on-screen keyboard, especially on smaller screens. But there’s no such concern in the desktop app.
If you have some other use-case that you feel can’t be addressed by the suggestions above, please let us know what that is.
What do you mean? Cards aren’t encrypted to the best of my knowledge, they can easily be viewed by exporting as plain text, looking into the database or just using the in-app edit functionality.
None of those reasons explain your use-case though. And with all due respect – they look like they were written by some LLM/AI/chatbot that doesn’t understand Anki very well. [If you feel the need to use that tool to express yourself in English, please make sure it’s at least giving us your ideas – not its own.]
#1, 2, and 4 sound like they would be solved by removing the unwanted type-answer boxes from your templates – as I suggested above.
#3 sounds like a problem with your note type.
#5 either doesn’t make any sense, or has nothing to do with this.
I’m unaware of any way they can prevent you from editing them once you’ve imported them into Anki.
I appreciate your feedback, but these points are entirely my genuine hands‑on experience with Anki, not generic AI‑generated content. Let me clarify my actual use case directly:
For #1, #2 and #4: While editing individual card templates can remove typing boxes, I maintain dozens of note types and decks. A global setting to disable typing answers is a one‑click system‑wide optimization, far more efficient than repeated manual template edits. It also prevents accidental keyboard input interference during fast‑paced review, an issue template tweaks cannot fully resolve.
For #3: The Enter‑key lag happens consistently across all my decks, not just one specific note type. This confirms the lag is tied to the typing‑answer feature itself, rather than flawed note design.
For #5: Eliminating redundant input steps and input‑related glitches directly creates a smoother, more stable review workflow. This is precisely my core demand and highly relevant to the setting.
Your template‑editing suggestion is reasonable for single‑deck use, but my workflow requires cross‑deck bulk optimization. Disabling typing answers is simply the most practical solution for my daily review. Also, the resources purchased from the Anki Chinese website (https://file.ankichinas.cn) are indeed encrypted. They only allow you to type answers, and you cannot remove the answer input field. You can go and test it for yourself. Furthermore, the seller restricts the number of devices you can use the deck on to 4 devices.
Do all of your decks come from that site and are encrypted in some way?
As far as I can tell from the above, this restriction only refers to the v2 encryption which is for other apps, not the Anki, and, as such, not relevant to this discussion.
As for v1 encryption, it says it is implemented using card scripts, which can’t pose any restrictions on editing the templates or exporting cards. What does it show when you press the Cards button in the editor? Or when you use Notes → Export Notes?
Thanks for your help!
Yes, almost all of them come from this website and have been encrypted.
Clicking the card can display the code, but the code is encrypted. The input box cannot be modified or deleted. The detailed code is shown below:
The front:
In Anki, the {{type:FieldName}} tag creates a text input box during reviews, allowing you to type your answer and immediately compare it to the correct field content. It works by adding the tag to the front template (creates the box) and back template (shows comparison)
and possibly caused by the encryption/decryption scripts, not the typing feature. #5 and “input‑related glitches” is probably caused by that as well. While #1,2, and 4 can be fixed with @kaiu’s advice (using script to modify all note types, if necessary).
Not sure what you mean. The code you posted looks normal. It is missing the encryption/decryption functions themselves, however. Are they in the Styling tab?