Quasar ships with a layout engine that removes a lot of repetitive CSS and lets you focus on structure. If you have ever fought with sticky headers, resizing drawers, or mobile breakpoints, this guide will help you use Quasar's layout primitives the way they were intended.
QLayoutQLayout is the root container for headers, drawers, footers, and pages. It manages the viewport and lets those pieces behave consistently across routes.
<template>
<QLayout view="hHh lpR fFf">
<QHeader bordered>Header</QHeader>
<QDrawer v-model="leftOpen" bordered>Menu</QDrawer>
<QPageContainer>
<QPage class="q-pa-lg">Page content</QPage>
</QPageContainer>
</QLayout>
</template>
<script setup lang="ts">
const leftOpen = ref(false);
</script>Key takeaways:
QLayout per route layout.view prop to define the relationship between header, footer, and page.QHeader and QDrawer as direct children of QLayout.QPage + QPageContainerA common mistake is rendering scrollable content outside of QPageContainer. The fix is simple:
QPageContainer.QPage.This ensures you get proper scrolling, correct header offsets, and predictable overflow. If you'd rather start from a finished shell, the Quasar drawer layouts and stacked layout blocks are built on QLayout with this structure.
Drawers should feel natural on desktop and mobile. In Quasar that means:
v-model to control open state.:breakpoint to match your design system.show-if-above when you want desktop drawers always visible.If you want a fast baseline, follow this pattern:
QHeader with a toolbarQDrawer that collapses below 1024pxQPage content inside QPageContainerThis gives you:
Responsive layouts help SEO by preventing CLS issues. Use fixed heights for headers and keep your layout structure stable so content does not jump.
Quasar's layout system is not just a convenience. It is a performance and UX advantage. Build around QLayout, keep your hierarchy clean, and your app will be consistent from mobile to desktop. For a complete app built on this structure, see the Rambo dashboard template.