Feature Library

Arrange any page in place

0.35 CPU ms
A still of the Arrange any page in place demo
Still
The live demo starts when it’s in view.Drag anything on the page · corners resize, sides set the width · Shift or Ctrl adds · arrows nudge · M turns arranging off

Move, resize, hide, line up and spread the parts of any live HTML page, like shapes on a slide: smart guides and equal gaps, several at once, the keyboard too, and undo.

What it costs a frame

0.35 ms
GPU
not used
CPU, median
0.35 ms
CPU, 95th pct
0.78 ms
Draw calls
0
Weight
Light

Measured 11 November 2026 on 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 157, 1920×1080 at 1×. 600 frames × 3 rounds, median kept. What ran: Measured with the demo arranging by itself: synthetic pointer events press a feature card, carry it in a slow loop for 48 frames (every frame places it, snaps it to its neighbours’ edges, middles and equal gaps, and moves the guides and handles) and drop it, then rest 12 frames, going round the three cards. Nothing runs between changes. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
unknown GPU · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed0.350.78
apple · Apple A19 Proin a browser tab · 16 November 2026not timed0.772.94
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed0.812.01

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. Slide and deck editors
  2. Tweaking a generated or templated page by hand
  3. Landing page and email builders
  4. Dashboards people lay out themselves
  5. Design reviews on the live page

Pitfalls, in brief

  1. Import arrange-in-place.base.css (and the look, or your own): without it nothing stops transitions while arranging, a hidden part does not show faint, and touch drags scroll the page.
  2. Mark the parts you edit with data-edit or data-item (or pass your own anchors).
  3. Two elements with the same anchor value are told apart by their order.
  4. Offsets are on CSS translate and scale, composed with the design’s own.
  5. Pick a unit that scales the way the page does: vw for a page as wide as the window, a custom property such as --u (1% of a fixed-size slide) for a scaled canvas.
4 more in brief
  1. Moves divide by the scale of every box around the part (transform, scale, zoom): a rotated or skewed parent is measured by its scale alone, so moves inside it go the wrong way.
  2. While arranging the root swallows clicks and takes its focusable parts out of the Tab order; give the toolbar layer a positioned element outside the root (or the body) so its buttons stay reachable.
  3. A framework that rewrites a placed element’s inline style (a style prop) wipes its placement until the next apply(): keep translate, scale, width and visibility out of the style you render, or call apply() after it renders.
  4. A hidden part is visibility: hidden, so a child with visibility: visible of its own still shows.
9 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From DeckStudio. Fully custom code.

WAI-ARIA Authoring Practices Guide (W3C): The toolbar pattern: one Tab stop, the arrow keys move inside it.

arrangedragresizesmart guidessnappingequal spacingaligndistributemulti-selectundokeyboardlive regioncss translatedomno dependencies

Near it in the frame