Why use k8size
- Cores ↔ millicores. Enter decimal cores, integer millicores, or paste
500m/0.5— see both forms plus YAML. - Mi vs M warning. Decimal suffixes trigger a warning and a one-click switch to the binary unit (256M → 256Mi).
- Shareable calculations. Copy a link with
?cpu=and?mem=for chats and tickets. - Single-container QoS. Guaranteed / Burstable / BestEffort from request/limit fields — not a sizing advisor.
- YAML snippets ready to paste. Copy
cpuandmemorylines for requests and limits. - Runs in the browser. No API; values never leave your device.
- Free and multilingual. No account; UI and SEO in every supported locale.
How to convert Kubernetes units
- Type a number or paste a full quantity (
500m,256Mi). - If you used a decimal memory unit, read the warning and switch to Mi/Gi when needed.
- Copy YAML or use Share to send a
?cpu=&mem=link. - Optionally fill request/limit fields in the QoS panel and check the class.
Units, requests and limits
Kubernetes accepts CPU as cores or millicores (m) and memory as binary (Ki/Mi/Gi/Ti) or decimal (k/M/G/T) suffixes. This tool only converts quantities — it does not recommend how large requests should be.
Tips:
- 1 core = 1000 millicores;
500mequals0.5. - Mi/Gi use powers of 1024; M/G/MB/GB use powers of 1000.
- requests guide scheduling; limits cap usage — usually requests ≤ limits.
- Equal CPU and memory requests and limits yield Guaranteed QoS.
- Prefer the same unit style across a team to avoid Mi vs M mistakes.
- This is not a workload sizing advisor — measure real usage separately.
- Decimal M/G/MB trigger a warning — you often want Mi/Gi.
- A ?cpu=&mem= link is handy for tickets and reviews.
What it is for
- checking millicores vs cores before editing a Deployment;
- comparing Mi and M when reading charts or manifests;
- preparing YAML fragments for requests and limits;
- teaching the difference between binary and decimal suffixes;
- quick sanity checks during reviews or incidents.
FAQ
What does the m suffix mean for CPU?
Millicores: 1000m equals one full core. Fractional cores like 0.5 equal 500m.
Is Mi the same as M or MB?
No. Mi is 1024² bytes; M and MB are 1000² bytes. Mixing them changes the real size.
Does the tool upload my values?
No. Conversion runs only in your browser.
Can it suggest the right requests for my app?
No. It converts units and shows a short tip — not a sizing advisor.
Which YAML form should I use for CPU?
Both 500m and 0.5 are valid; pick one style and stay consistent.
Are KB/MB/GB supported?
Yes, as 1000-based aliases alongside K/M/G/T.
What about Ti and T?
Ti is 1024⁴ bytes; T/TB are 1000⁴. Both appear in the memory table.
Is Guaranteed QoS required?
No. It is one QoS class when requests equal limits for CPU and memory.
Does it edit full manifests?
No. It only converts units and offers short YAML snippets.
Is the service free?
Yes — free, no registration, no conversion limits.
What does the M vs Mi warning do?
If you pick a decimal unit (M/G/MB…), the tool reminds you that manifests often mean binary Mi/Gi and offers to switch.
How do I share a calculation?
Click Share to copy a URL with ?cpu= and ?mem=. Opening the link restores the same values.
What does the QoS panel show?
A simplified Guaranteed / Burstable / BestEffort class for one container from request/limit fields — not a workload sizing recommendation.