Convert litres to Shō (升)
East Asia · East Asian Volume · active · modern
Conventional value The unit is customary but its modern value is settled and widely cited; the arithmetic itself is exact.
Quick answer
1 litre = 0.554324 Shō (升)
1 litre = 0.554324 Shō (升). Shō (升) is a traditional volume unit from East Asia.
Convert any amount
litres to Shō (升) table
| litres | Shō (升) |
|---|---|
| 0.25 litres | 0.138581 Shō (升) |
| 0.5 litres | 0.277162 Shō (升) |
| 1 litre | 0.554324 Shō (升) |
| 2 litres | 1.10865 Shō (升) |
| 3 litres | 1.66297 Shō (升) |
| 4 litres | 2.21729 Shō (升) |
| 5 litres | 2.77162 Shō (升) |
| 10 litres | 5.54324 Shō (升) |
| 20 litres | 11.0865 Shō (升) |
| 25 litres | 13.8581 Shō (升) |
| 50 litres | 27.7162 Shō (升) |
| 100 litres | 55.4324 Shō (升) |
About the Shō (升)
Japanese volume. 1 Shō = 10 Gō ≈ 1.8 liters.
- Symbol
- 升
- Value in SI
- 1 Shō (升) = 1.804 litre
- Typical use
- cooking, trade
- Source
- UnitConvertLab measurement atlas
Every atlas conversion routes through the SI litre. See our methodology and data provenance pages for how these values are sourced and verified.
Frequently asked
How many Shō (升) are in a litre?
1 litre = 0.554324 Shō (升). Multiply the number of litres by 0.55432373 to get Shō (升).
What is Shō (升) used for?
Japanese volume. 1 Shō = 10 Gō ≈ 1.8 liters. It is classified as active and dates from the modern period.
Is the Shō (升) value exact?
Yes for practical purposes. UnitConvertLab converts every atlas unit through the SI litre, so the arithmetic itself introduces no rounding beyond the digits shown.
How reliable is this Shō (升) conversion?
Conventional value — The unit is customary but its modern value is settled and widely cited; the arithmetic itself is exact. Source: UnitConvertLab measurement atlas.
Cite this page
UnitConvertLab. (2026). Convert litres to Shō (升). UnitConvertLab. Retrieved from https://unitconvertlab.com/regional/liter-to-sho
Report an incorrect value or source
Regional units vary by district and by century. If this figure, its variant list or its citation is wrong where you are, tell us — the report carries the page context automatically.