Getting the Most Out of Your TRUE Flask

A few practical notes on using your TRUE Flask, covering output levels, cleaning, and charging, so you're getting what the device is actually built to deliver.

Choosing your output level

TRUE Flask is dual-mode. Tap twice on the touchscreen to run a cycle at 6,000 PPB. If you want to go higher, run the cycle again right after for up to 10,000 PPB total. There's no need to go higher than you're comfortable with. Both levels run the same underlying electrolysis process, just for a longer combined cycle time.

Cleaning and descaling

Like any electrolysis device, TRUE Flask benefits from regular cleaning to keep the membrane performing consistently. We recommend running a cleaning cycle with a TRUE Cleaning Tablet roughly every 2 to 4 weeks depending on how hard your water is, more often if you're in a hard water area. Skipping this is the single most common reason output drops over time; it's a maintenance issue, not usually a defect.

Charging

TRUE Flask ships with a wireless charging dock. The bottle sits upright on the base to charge; it won't charge lying on its side or off the dock. A full charge supports 30+ cycles before you need to recharge, so daily use shouldn't mean daily charging for most people.

Storage

Store the bottle upright when not in use, and avoid leaving water sitting in it for extended periods between cycles. The bottle doesn't need to be refrigerated; hydrogen gas dissipates from water over time regardless of temperature, so the general guidance for any hydrogen water is to drink it relatively soon after a cycle rather than letting it sit for hours.

When something's actually wrong vs. normal behavior

A small amount of water or moisture around the base after a cycle is normal, that's the oxygen byproduct venting. Significant leaking, an unresponsive touchscreen after a restart, or output that doesn't improve after a full cleaning cycle are the signs of an actual issue. If you're seeing any of those, our Warranty Claim Review page walks through troubleshooting first and the claim process if it's still not right.