view · edit Frequently asked questions Q: When using {{convert}} why does the answer sometimes seem a bit off? A: This template takes into account the precision of the supplied value and generally rounds the output to the same level of precision. If you need to change from the default output precision, see rounding. Note: This can cause whole numbers that end in one or more zeroes to be converted less accurately than expected. Q: What are all the possible units (kg, lb, m, cm, ft, in, °C, °F, km, mi, nmi, mph, km/h, and so on)? A: See Help:Convert units for an introduction and Module:Convert/documentation/conversion data for the complete list. Q: I've been using Convert for some time and am pretty comfortable with its basic features. Does it have other features which it would be worth my while to learn about? A: Almost certainly. Start with Help:Convert. For more, see the FAQ.

Template:Convert is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories. Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases.

Archives

Archive 1 Archive 2 Archive 3

This page has archives. Sections older than 42 days may be automatically archived by Lowercase sigmabot III when more than 2 sections are present.

Template:Convert

... in conception

... and in reality

Is it possible to display a shorter version than

{{convert|149.6x71.5x8.25|2|mm|2}}

149.6 by 71.5 by 8.25 millimetres (5.89 in × 2.81 in × 0.32 in)

Or?

{{convert|149.6x71.5x8.25|mm|2|abbr=on}}

149.6 mm × 71.5 mm × 8.25 mm (5.89 in × 2.81 in × 0.32 in)

In some infoboxes (eg, {{Infobox mobile phone}}), where space is limited, it is desired to list the dimensions of some object, and its conversion, but it seems unnecessary to list the “mm” and the “in” three times. I might be missing something, but I would like an option to display something like:

149.6 × 71.5 × 8.25 mm (5.89 × 2.82 × 0.32 in)

— HTGS (talk) 23:14, 6 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241106231400","author":"HTGS","type":"comment","level":1,"id":"c-HTGS-20241106231400-Multiple_values,_shorter_abbreviation?","replies":["c-Stepho-wrs-20241106234900-HTGS-20241106231400"]}}-->

Use xx instead of x.

{{convert|149.6xx71.5xx8.25|mm|2}} gives 149.6 × 71.5 × 8.25 mm (5.89 × 2.81 × 0.32 in)

Beware that this technically violates MOS:UNITSYMBOLS. |by| is an option that obeys the MOS (but looks clumsier).

{{convert|149.6|by|71.5|by|8.25|mm|2}} gives 149.6 by 71.5 by 8.25 mm (5.89 by 2.81 by 0.32 in)  Stepho  talk  23:49, 6 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241106234900","author":"Stepho-wrs","type":"comment","level":2,"id":"c-Stepho-wrs-20241106234900-HTGS-20241106231400","replies":["c-HTGS-20241107000600-Stepho-wrs-20241106234900"],"displayName":"Stepho"}}-->

Thank you! I might actually ask at MOSNUM, because this feels like an oversight (for use in small spaces), and I’d like to standardise this across a lot of infoboxes. — HTGS (talk) 00:06, 7 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241107000600","author":"HTGS","type":"comment","level":3,"id":"c-HTGS-20241107000600-Stepho-wrs-20241106234900","replies":[]}}-->

I'm not sure if this is the right place to discuss this, but is it possible to integrate troy weight into this template? Basically another obscure, antiquated unit of mass that still sticks around out of tradition in the precious metals industry. TheTechnician27 (Talk page) 12:23, 10 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241110122300","author":"TheTechnician27","type":"comment","level":1,"id":"c-TheTechnician27-20241110122300-Troy_weight","replies":["c-Redrose64-20241110154800-TheTechnician27-20241110122300"]}}-->

@TheTechnician27: It's already provided, e.g. {{convert|1|ozt|g|3}} → 1 troy ounce (31.103 g). See full list of mass units. --Redrose64 🌹 (talk) 15:48, 10 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241110154800","author":"Redrose64","type":"comment","level":2,"id":"c-Redrose64-20241110154800-TheTechnician27-20241110122300","replies":["c-TheTechnician27-20241110172600-Redrose64-20241110154800"]}}-->

@Redrose64: Oooh, thank you! I was trying to use 'oz t' with no success. TheTechnician27 (Talk page) 17:26, 10 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241110172600","author":"TheTechnician27","type":"comment","level":3,"id":"c-TheTechnician27-20241110172600-Redrose64-20241110154800","replies":[]}}-->

Moved from Module talk:Convert. Johnuniq (talk) 01:45, 19 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241119014500","author":"Johnuniq","type":"comment","level":2,"id":"c-Johnuniq-20241119014500-Indian_numbering_system:_lakhs_and_crores","replies":[]}}-->

I request that we enhance the module to include lakhs and crores.

The Indian numbering system is the main nomenclature used in South Asia to name large numbers. From the lead:

The terms lakh or 1,00,000 (one hundred thousand, written as 100,000 in Pakistan, and outside the Indian subcontinent) and crore or 1,00,00,000 (ten million, written as 10,000,000 outside the subcontinent) are the most commonly used terms in Indian English to express large numbers in the system.

This is a dimensionless unit, or if you wish, the units are integers. (Hence if implemented, the data item in 'all_units' at Module:Convert/data could be named ["ins"] for 'Indian numbering system'). Note also the main pattern of comma-separation into groups of two and three digits, not just three.

These terms should be converted to standard English terms, mostly with the term million, except for values up to 9 lakh, which could be 900,000. Sample usage in articles:

• lakh – 6,914 articles
• crore – 10,809 articles

The plural sometimes has the -s, and sometimes doesn't; so both '2 lakhs' and '2 lahk' are seen; same for crore(s).

This arose at the Rfc at Wikipedia talk:Manual of Style/Dates and numbers, where in my !vote (diff) I called for using template {{Convert}}, only to realize after the fact that the template will not handle it. This conversion is badly needed, as it will resolve a sore point about usage of lakhs and crores in many articles. Thanks, Mathglot (talk) 23:46, 18 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241118234600","author":"Mathglot","type":"comment","level":1,"id":"c-Mathglot-20241118234600-Indian_numbering_system:_lakhs_and_crores","replies":["c-Johnuniq-20241119020300-Mathglot-20241118234600"]}}-->

Earlier discussions.

• Template talk:Convert/Archive 2#Lakh
• Template talk:Convert/Archive 2#110 crore tonnes
• Template talk:Convert/Archive 3#Crore
• Template talk:Convert/Archive 3#Lakh and crore

I have not yet examined the RfC at WT:Manual of Style/Dates and numbers#RfC Indian numbering conventions. The above discussions point out that lakh and crore are not units. They are like million which is also not a unit. However, if convert could do something useful that is not provided by {{lakh}} and {{crore}}, it could be investigated. Johnuniq (talk) 02:03, 19 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241119020300","author":"Johnuniq","type":"comment","level":2,"id":"c-Johnuniq-20241119020300-Mathglot-20241118234600","replies":["c-Stepho-wrs-20241119230700-Johnuniq-20241119020300"]}}-->

The {{lakh}} and {{crore}} templates make more sense than overloading {{convert}}.  Stepho  talk  23:07, 19 November 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241119230700","author":"Stepho-wrs","type":"comment","level":3,"id":"c-Stepho-wrs-20241119230700-Johnuniq-20241119020300","replies":[],"displayName":"Stepho"}}-->

It is NOT accurate! 8000 nmi = 14,816 km not 15000. Check google & ref64 Bombardier Global 7500. The correct multiplier is 1.852 not 1.875 see ref 1 Nautical mile & for at least half a century (ref 5). Dave-okanagan (talk) 04:18, 17 December 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241217041800","author":"Dave-okanagan","type":"comment","level":1,"id":"c-Dave-okanagan-20241217041800-Nautical_miles_to_Kilometers","replies":["c-Stepho-wrs-20241217045600-Dave-okanagan-20241217041800","c-Imzadi1979-20241217054100-Dave-okanagan-20241217041800"]}}-->

The template sees 3 zeroes at the end and assumes that is the amount of rounding desired. Ie 8000 nmi +/- 500 nmi. It is not assuming 8000 nmi +/- 0.5 nmi. Therefore it rounds the output to a similar amount.

However, you can control the rounding. Eg:

• {{cvt|8000|nmi|km|0}} gives 8,000 nmi (14,816 km) (probably not appropriate if the 8000 is a round number)
• {{cvt|8000|nmi|km|-1}} gives 8,000 nmi (14,820 km)
• {{cvt|8000|nmi|km|-2}} gives 8,000 nmi (14,800 km)
• {{cvt|8000|nmi|km|-3}} gives 8,000 nmi (15,000 km) (probably the most appropriate if the 8000 is a round number)

Choose whichever suits the situation best. Be careful of false precision. Stepho  talk  04:56, 17 December 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241217045600","author":"Stepho-wrs","type":"comment","level":2,"id":"c-Stepho-wrs-20241217045600-Dave-okanagan-20241217041800","replies":[],"displayName":"Stepho"}}-->

@Dave-okanagan: this is discussed in the first FAQ at the top of the page as well. Imzadi 1979 → 05:41, 17 December 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241217054100","author":"Imzadi1979","type":"comment","level":2,"id":"c-Imzadi1979-20241217054100-Dave-okanagan-20241217041800","replies":[],"displayName":"Imzadi\u00a01979"}}-->