Generate a step-by-step conversion between bits, bytes, kilobytes, megabytes, gigabytes, and terabytes, explaining why storage math uses base 2 instead of base 10.
You are a computer science tutor who never states a storage conversion without showing the actual multiplication or division that produces it, since a memorized conversion table falls apart the moment someone asks for an unfamiliar combination. My conversion is [CONVERSION], stated plainly, such as convert 4 gigabytes to megabytes, how many bytes are in a bit, or convert 2500 megabytes to gigabytes. If I left that blank, ask me for a specific conversion instead of walking through a random example in its place. My unit system is [SYSTEM:select:the common 1024-based system most operating systems actually use,the strict decimal 1000-based system used on storage packaging]. State plainly that these two systems disagree and that this is the actual reason a drive labeled 1 terabyte shows up as roughly 931 gigabytes in your operating system, before doing any math, so the discrepancy is explained rather than left as a mystery. Solve [CONVERSION] using [SYSTEM], showing the specific multiplication or division step by step, one unit boundary at a time if the conversion spans more than one step, such as converting gigabytes to kilobytes by going through megabytes rather than jumping straight there with a single memorized number. State the final answer clearly on its own line. Explain briefly why storage uses powers of 2, 1024 rather than 1000, tracing it back to binary, 2 to the 10th power lands close to 1000 which is why the prefix kilo got reused for it, and name that this reuse of decimal prefixes for binary values is exactly what caused the packaging-versus-operating-system mismatch. My depth is [DEPTH:select:just the conversion,also cover bits versus bytes and why file sizes use bytes but internet speeds use bits]. If I chose the second option, explain that a byte is 8 bits, why file sizes are conventionally measured in bytes, and why internet connection speeds are conventionally measured in bits, which is the specific reason a 100 Mbps connection downloads a 100 megabyte file in roughly 8 seconds, not 1, if nothing else is happening on the network. If I ask to convert a real file size or download time using this math, walk through that specific scenario with actual numbers instead of speaking about it in the abstract.
Use this prompt anywhere
10,000+ expert prompts for ChatGPT, Claude, Gemini, and wherever you use AI.
Get Early AccessA 1 terabyte drive shows up as roughly 931 gigabytes on your computer, and almost nobody gets told why. This tool solves any storage unit conversion with the actual math shown, explaining why the number on the box never quite matches the number your operating system reports.
State [CONVERSION], convert 4 gigabytes to megabytes, how many bytes in a bit, whatever you need, and pick [SYSTEM], the 1024-based system your operating system actually uses, or the strict 1000-based decimal system used on packaging. The output states that disagreement up front, then solves your conversion step by step, one unit boundary at a time. It also explains why storage uses powers of 2 in the first place, tracing kilo, mega, and giga back to binary. Set [DEPTH] to also cover bits versus bytes, and why a 100 Mbps connection doesn't download a 100 megabyte file in one second.
Ask it to work through a real file size or download time and get actual numbers, not an abstract explanation. Once units click, see how those bytes actually move across a network in the OSI model layer explainer, or check how individual characters get encoded in the ASCII and Unicode explainer.
Run it in the Dock Editor to keep a running reference of the conversions you actually needed.
Once it is running in the Dock Editor, ChatGPT, Claude, or Gemini, fill in [CONVERSION] with the exact units you're converting between, gigabytes to megabytes, bytes to bits, whatever the real question is.
Set [SYSTEM] to the 1024-based system operating systems use, or the 1000-based decimal system used on storage packaging, since they disagree.
Before any math, get the plain reason a labeled 1TB drive shows less than 1TB in your operating system, so the mismatch makes sense.
See the actual multiplication or division for your conversion, broken into one unit boundary at a time for multi-step conversions.
Set [DEPTH] to also cover bits versus bytes to understand why file sizes and internet speeds get measured in different units entirely.
Understand the actual math behind storage unit conversions instead of memorizing a table that breaks down on an unfamiliar combination.
Get a clear, math-backed explanation for why a 1TB drive shows up as roughly 931GB in a computer's file system.
Convert an internet speed in megabits to an actual download time for a file measured in megabytes, with the real math shown.
Reinforce binary-based unit conversions and the bits-versus-bytes distinction that shows up constantly in entry-level certification exams.
Discover more prompts that could help with your workflow.
Build a small working program that calls a real public API, with the request, response, and API key setup explained step by step.
Explain a core functional programming idea, such as pure functions or immutability, with a broken code example and its fixed version shown side by side.
Explain a built-in math function, square root, power, absolute value, or rounding, covering math and syntax, then generate practice calls to predict before revealing results.
10,000+ expert-curated prompts for ChatGPT, Claude, Gemini, and wherever you use AI. Our extension helps any prompt deliver better results.