Introduction

DialogFragment does not usually take its final size from the XML layout alone. To control width and height reliably, you typically update the dialog window after it has been created and attached, most often in onStart.

Why Layout XML Is Often Not Enough

A dialog lives inside a window managed by the framework. Even if the root view in your dialog layout says match_parent or a specific dp size, the surrounding dialog window may still impose its own dimensions. That is why developers often see a custom layout render smaller than expected.

The reliable fix is to set the window size directly once the dialog exists.

Setting Size in onStart

The most common approach is to override onStart and call setLayout on the dialog window.

1import android.app.Dialog
2import android.os.Bundle
3import android.view.LayoutInflater
4import android.view.View
5import android.view.ViewGroup
6import androidx.fragment.app.DialogFragment
7
8class ConfirmDialogFragment : DialogFragment() {
9
10    override fun onCreateView(
11        inflater: LayoutInflater,
12        container: ViewGroup?,
13        savedInstanceState: Bundle?
14    ): View {
15        return inflater.inflate(R.layout.dialog_confirm, container, false)
16    }
17
18    override fun onStart() {
19        super.onStart()
20        dialog?.window?.setLayout(
21            ViewGroup.LayoutParams.MATCH_PARENT,
22            ViewGroup.LayoutParams.WRAP_CONTENT
23        )
24    }
25}

This is a good default for dialogs that should be wide but sized vertically according to their content.

Using Exact Dimensions in dp

If you want a fixed size, convert dp to pixels before calling setLayout.

1import kotlin.math.roundToInt
2
3private fun dpToPx(dp: Int): Int {
4    val density = requireContext().resources.displayMetrics.density
5    return (dp * density).roundToInt()
6}
7
8override fun onStart() {
9    super.onStart()
10    dialog?.window?.setLayout(
11        dpToPx(320),
12        dpToPx(240)
13    )
14}

This keeps the dialog visually consistent across screen densities.

Percentage-Based Width

Fixed dimensions are not always ideal on tablets or very small phones. A common responsive pattern is to make the width a percentage of screen width while leaving height flexible.

1override fun onStart() {
2    super.onStart()
3
4    val width = (resources.displayMetrics.widthPixels * 0.9).toInt()
5    dialog?.window?.setLayout(
6        width,
7        ViewGroup.LayoutParams.WRAP_CONTENT
8    )
9}

Using a percentage often produces better results than a single hard-coded width.

When a Full-Screen Dialog Is the Better Choice

If your content needs most of the screen, forcing a floating dialog to behave like a full page is usually the wrong abstraction. At that point, a full-screen dialog theme or a normal Fragment screen often gives cleaner layout behavior and fewer sizing hacks.

That distinction helps keep small confirmation dialogs simple while giving larger workflows the room they actually need.

Styling and Background Considerations

Dialog appearance is affected by theme and window background as well as by size. If the dialog still looks too small, check whether the root layout has extra margins or whether the window background adds padding. A transparent background is sometimes useful when you want tighter control over the visible content bounds.

1override fun onCreateDialog(savedInstanceState: Bundle?): Dialog {
2    return super.onCreateDialog(savedInstanceState).apply {
3        window?.setBackgroundDrawableResource(android.R.color.transparent)
4    }
5}

This does not change the size on its own, but it can remove default visual padding that makes the dialog appear narrower or shorter.

Common Pitfalls

Setting width and height too early, such as inside onCreateView, may fail because the window is not ready yet.

Assuming the layout XML alone controls dialog size is a common misconception. The dialog window still participates in measurement.

Hard-coded pixel values create inconsistent results across devices. Convert from dp or use a percentage-based width.

Using MATCH_PARENT for height can make dialogs feel like full-screen panels when WRAP_CONTENT would be more appropriate.

Theme padding and default dialog backgrounds can make a correctly sized dialog look smaller than intended.

Summary

• 'DialogFragment size is usually controlled through the dialog window, not just layout XML.'
• Override onStart and call dialog?.window?.setLayout(...) for reliable sizing.
• Use MATCH_PARENT, WRAP_CONTENT, dp conversion, or a width percentage depending on the design.
• Check theme padding and backgrounds if the dialog still looks off.
• Prefer responsive sizing over fixed pixels when the dialog must work across devices.