#1 India's Top IT Training Institute

×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
☸️ FREE · CPU · MEMORY

Kubernetes Units Converter: Mi vs M and 250m Explained

Type a resource quantity from your manifest and see it in every other unit.

  • 🧠 Mi, Gi, M, G and bytes
  • ⚙️ Millicores and cores
  • 🚩 Catches the lowercase m typo

How to use the Kubernetes CPU and Memory Units Converter

  1. 1. Pick CPU or memoryChoose which kind of quantity you are converting.
  2. 2. Type the valueAs written in YAML, for example 512Mi, 1G or 250m.
  3. 3. Read the tableSee the same amount in bytes and every common unit.

Worked example: 1Gi

The default 1Gi is 1,073,741,824 bytes, because Gi is a binary unit: 1024 × 1024 × 1024. That is 1,024Mi, but about 1,073.74M in decimal megabytes. If you write 1G instead you get exactly 1,000,000,000 bytes, roughly 7% less. The difference matters when you set memory limits close to what an app really needs.

For CPU, 250m means 250 millicores, a quarter of one core, and is the same as writing 0.25. One CPU in Kubernetes is one vCPU on a cloud VM or one hyperthread on bare metal.

Mistakes this catches

  • Lowercase m on memory: 128m means 128 millibytes, which is 0.128 bytes. Kubernetes accepts it, but it is almost always a typo for 128Mi.
  • Lowercase ki: the valid binary suffix is Ki; the tool rejects ki.
  • Fractions of a millicore: 0.5m is not allowed; the smallest CPU step is 1m.
  • Exponent form: values such as 129e6 are valid and converted.

Requests decide where a Pod is scheduled and limits cap it, so getting units right avoids Pods that never schedule or containers killed for using too much memory. Set requests from what monitoring shows the app really uses, then add headroom for limits. Put the values into a manifest with the Kubernetes YAML generator, and convert transfer sizes with the bandwidth calculator.

Frequently asked questions

Should I use Mi or M?

Mi is the usual choice, because it matches how operating systems and container runtimes report memory. Just be consistent.

What happens if a container uses more memory than its limit?

The kernel kills it (OOMKilled) and Kubernetes restarts it according to the Pod's restart policy.

Is the Kubernetes CPU and Memory Units Converter free?

Yes, the Kubernetes CPU and Memory Units Converter is free. The first time you see your first result, you are asked for your name and WhatsApp number once. After that, this and every other Uncodemy tool opens straight away without the form.

More free tools

See all free tools