Picture a hypothetical worksheet problem (illustrative only, not a real assignment): find the area of three rectangles, then add them together for a total. The math for each rectangle is trivial — length × width — but if you calculate each one, write the result on scratch paper, then retype all three into a final addition, you've introduced three separate chances to fumble a digit. Memory, Ans, and history are the tools that remove that retyping step entirely.
Memory keys: M+, M-, MR, MC
Back to the three-rectangle example: calculate the first rectangle's area and press M+ — that value is now stored. Calculate the second and press M+ again — memory now holds the running sum of both. Do the same for the third. When you're done, press MR to recall the combined total, or just read it straight off the memory badge. You never retyped a single subtotal by hand.
M- is the mirror case: useful when you're tracking a value that should go down as you subtract items, like working through a hypothetical example budget where you calculate several deductions and want a running "amount remaining" instead of a running sum. Press MC whenever you start a new, unrelated problem — memory persists across separate calculations until you clear it, which is exactly the point, but it also means an old value can linger and quietly throw off a new problem if you forget to reset it.
The Ans key vs. memory
These two features look similar but solve different problems. Ans is built for a straight chain of steps where each one feeds directly into the next: calculate a value, then immediately use Ans in the next expression to build on it, e.g. squaring your last result with Ans^2 or adding ten percent to it with Ans * 1.1. Memory is built for holding onto a number while you go do other, unrelated calculations in between — the value in memory doesn't change no matter how many other expressions you type and solve, until you explicitly update it.
A practical rule of thumb: if the next calculation is a direct continuation of the last one, reach for Ans. If you need to park a number, do several other things, and come back to it later, use memory instead.
Calculation history and rerunning a problem
History is especially useful for a study-group or self-check workflow: work through a problem, get an answer, then a few steps later realize you want to double-check an earlier step. Instead of re-deriving the whole expression from memory, scroll the history list, click the earlier entry, and it's back in the display ready to inspect or rerun. Because history is scoped to the current browser session (it isn't sent anywhere and isn't saved permanently), it resets when you close the tab — treat it as a scratch pad for one sitting, not permanent storage.
If you want to keep a specific result past the current session, use the shareable link feature described below rather than relying on history sticking around.
Fraction display and shareable links
3/4) alongside the decimal, whenever the result has a clean exact fractional equivalent. The shareable link feature encodes your typed expression into a URL, so opening that link reloads the same expression — useful for sending a specific calculation to someone else.Fraction display matters most for a specific case: a textbook or worksheet that expects an exact answer rather than a rounded decimal. 0.75 read as a decimal is fine for most purposes, but a worksheet asking "express as a fraction" wants 3/4 specifically. The toggle only shows a fraction when one exists cleanly — a result like an irrational square root has no short exact fraction, so it's left as a decimal even with the toggle on.
The shareable link solves a different, more social problem: getting a specific calculation to another person without them having to retype it. Copy the link after calculating, and whoever opens it sees the same expression loaded into their own calculator — nothing about the calculation is stored on a server in the process; the expression itself lives inside the link.