ThisCalculator

Everyday

Convert Minutes to Hours in Power BI: Quick Guide

Updated · Standard formula, shown below

The calculator for this page is switched off while it is checked. The formula is below, and the worked example in the article shows how to use it by hand.

Convert Minutes to Hours in Power BI: Quick Guide

To convert minutes to hours in Power BI, divide the minute value by 60 in a calculated column or measure. For example, a column named “Minutes” can be converted with the formula Hours = 'Table'[Minutes] / 60, returning a decimal number like 2.5 for 150 minutes.

Formula

The basic conversion formula is:

Hours = Minutes ÷ 60

Where:

  • Minutes = the numeric value representing elapsed time in minutes (unit: min)
  • Hours = the resulting time in hours, expressed as a decimal (unit: h)

For example, 90 minutes divided by 60 gives 1.5 hours. This formula works for any positive number of minutes, including fractions (e.g., 0.5 minutes = 0.00833 hours).

Worked Example

Using the default input of 150 minutes:

  1. Start with the minute value: 150 min
  2. Divide by 60: 150 ÷ 60 = 2.5
  3. Result: 2.5 hours (which is 2 hours and 30 minutes)

The calculator above shows the same result: 2.50 hours for the decimal output, and 2.30 for the hours-and-minutes format (2 hours and 30 minutes).

Why Convert Minutes to Hours in Power BI?

Power BI often stores duration data as raw minutes because that is how many source systems export it—call center software, manufacturing logs, or fitness trackers. But raw minutes are hard to read in reports; 1,440 minutes means nothing to most viewers, while 24 hours is instantly clear. Converting to hours also makes aggregation easier: summing hours directly gives a total that can be formatted as a number or a duration, whereas summing minutes then converting once at the end is more efficient.

Another reason is consistency. If some reports use hours and others use minutes, comparisons become error-prone. By standardizing on hours (or a clear hours-and-minutes format), you reduce misinterpretation.

How to Do It: Calculated Column vs. Measure

In Power BI, you have two main places to write the conversion: a calculated column or a measure. The choice depends on how you plan to use the result.

  • Calculated column – Use this when you need the converted value as a row-level attribute, for example to filter, group, or use in a slicer. Create it in the Data view by going to the table and selecting New Column. The formula is simple: Hours = 'Table'[Minutes] / 60.
  • Measure – Use this when you need a dynamic aggregation, like total hours for a selected date range. Measures are written in the Report view or Model view. For example: Total Hours = SUM('Table'[Minutes]) / 60. This measure sums all minutes in the current filter context and then divides by 60.

For most reporting scenarios, a measure is preferable because it respects slicers and filters. A calculated column is static—it does not react to user selections.

Formatting the Result: Decimal vs. Duration

After conversion, you need to format the output correctly. Two common formats are:

  • Decimal hours – e.g., 2.5 hours. This is useful for calculations (multiplying by an hourly rate) but not very human-friendly. To format, select the column or measure, go to the Format pane, and choose Decimal number with 1 or 2 decimal places.
  • Hours and minutes – e.g., 2h 30m. This is more readable but requires a bit more work. You can create a text column using DAX: Duration Text = INT('Table'[Minutes] / 60) & "h " & MOD('Table'[Minutes], 60) & "m". For a measure, wrap it in a FORMAT function if needed.

Alternatively, you can use Power BI’s built-in duration format. If you set the data type to Time or Duration (in some versions), the value may display as hours:minutes:seconds. However, this only works if the value is stored as a duration, not a plain number. A common trick is to divide minutes by 1440 (minutes in a day) and then format as Time—this shows the result as a clock time (e.g., 2:30 for 150 minutes), but that can be confusing because it looks like a time of day, not a duration.

Common Mistakes and Pitfalls

One frequent error is forgetting to divide by 60 and instead multiplying, or confusing minutes with seconds. Another is using integer division when you need decimals. In DAX, the division operator / always returns a decimal, but if you use INT() incorrectly, you might lose the fractional part.

Another pitfall is mixing data types. If your minute column is stored as text, you must convert it to a number first. Use VALUE('Table'[Minutes]) in the formula, or change the column type in the Query Editor.

Also, be careful with aggregation. If you create a calculated column that divides by 60, then sum that column, you get the correct total hours. But if you sum the original minutes and then divide by 60 in a measure, you get the same result—both are fine. However, if you average the converted column, you get the average hours per row, which is different from the average of the original minutes divided by 60 (though mathematically the same). The issue arises when you use a calculated column in a visual that doesn’t aggregate—it will show row-level values, which may not be what you want.

Alternatives: Using Power Query or DAX

You can also perform the conversion in Power Query (the data preparation tool) before loading data into the model. This is useful if you want the column to be part of the data model permanently. In Power Query, add a custom column with the formula [Minutes] / 60. The advantage is that the transformation is documented and repeatable when you refresh data.

In DAX, you have more flexibility for dynamic calculations. For example, you can create a measure that converts a duration stored in seconds to hours: Hours = SUM('Table'[Seconds]) / 3600. The same principle applies: divide by the number of units in an hour.

For advanced scenarios, you might want to display the result as a duration in the format “2h 30m� using DAX’s FORMAT function with custom format strings, but that is more complex and often not necessary for simple reporting.

Frequently Asked Questions

How do I convert minutes to hours and minutes in Power BI?

To show both hours and remaining minutes, create a calculated column or measure that computes the integer part as hours and the remainder as minutes. For example: Hours = INT('Table'[Minutes] / 60) and Minutes = MOD('Table'[Minutes], 60). You can then concatenate them into a text string like Hours & "h " & Minutes & "m".

Why is my result showing as a whole number instead of a decimal?

This usually happens because the column format is set to “Whole Number� or because you used the INT function. Make sure the column or measure format is set to “Decimal number� and that you are using the division operator / without wrapping in INT.

Can I convert minutes to hours in a measure that respects slicers?

Yes. Write a measure like Total Hours = SUM('Table'[Minutes]) / 60. This measure will automatically recalculate based on the current filter context from slicers, page filters, and report filters.

How do I display the result as “2h 30m� instead of 2.5?

Create a calculated column with the formula: Duration = INT('Table'[Minutes] / 60) & "h " & MOD('Table'[Minutes], 60) & "m". This will produce a text string. For a measure, you can use a similar approach with FORMAT if needed.

What if my minutes are stored as text?

Convert the text to a number first. In Power Query, change the column type to “Whole Number� or “Decimal Number�. In DAX, use VALUE('Table'[Minutes]) to convert the text to a number before dividing.

Is there a built-in function for this in Power BI?

There is no direct “convert minutes to hours� function, but you can use the basic arithmetic division as described. For more complex time formatting, you can use the FORMAT function, but it does not handle durations directly; you have to construct the string manually.

Related

Formula used
in t | Minutes | min | 150 | 0
out h | Hours (decimal) | h | t / 60 | 2
out hm | Hours and minutes | h | FLOOR(t / 60, 1) + (MOD(t, 60) / 100) | 2

Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.