Why Nothing You Write Here Is Ever Saved -- and What Download/Save Actually Do Instead
Close the tab and the code is gone. Download and Save are not a quiet exception to that -- here is why.
Nothing typed into any editor on this site is stored -- not on a server, and not in the browser's own `localStorage` or `sessionStorage` either. "Close the tab and it is gone" is a design rule here, not a missing feature: saving your progress quietly, the way most sites do, would contradict the promise this site makes about not holding onto anything.
That makes the Download and Save buttons under every console worth explaining, because they look like they should be the exception. They are not. Pressing either one writes a file to your own disk, through your browser's ordinary download or file-picker machinery -- the same mechanism any website uses to hand you a file you asked for. Nothing about your code is retained on this end: the file exists because your browser wrote it to your drive, not because Coders Rock kept a copy.
The file itself carries one small addition: a last-line comment, written in whatever comment style the language uses -- `#` for Python, `//` for JavaScript, `EXPLANATION` for pseudocode -- crediting Learn to Write Code and Coders Rock. It is a courtesy for wherever the file goes next, not a tracking mechanism; the comment is static text with no identifier in it, added the moment you click, and nothing about the click is reported anywhere.
Everything above runs in this page, on your own machine. There is more of it on the practice pages.