Get absolute position of child in scrolling frame

I want to know how I would get the child’s absolution position inside a scrolling frame including factors like AutomaticCanvasSize and also UI Modifier Instances.

Right now if I just get the absolute position of a child in a y axis scrolling frame, the x position would be correct but the y position would be wrong.

You need to add the ScrollingFrame’s current scroll offset to the child’s AbsolutePosition. AbsolutePosition alone ignores both CanvasPosition and UI modifiers.

A correct Y value looks like this:

local absPos = child.AbsolutePosition
local realY = absPos.Y + scrollingFrame.CanvasPosition.Y

If you use UIListLayout/UIGridLayout with AutomaticCanvasSize, this still works because the layout only affects the canvas size, not the offset.

I’ve modified your code a little bit and there’s still a little offset from the actual position

local scroll = script.Parent.ScrollingFrame
local child = scroll.Frame2

local y = child.AbsolutePosition.Y + scroll.CanvasPosition.Y + child.AbsoluteSize.Y
print(child.AbsolutePosition.X, y)


The orange is Frame2 and you can see how the purple still has a little offset on the y to Frame2’s position.

The x position is correct I just shifted it left.

The issue is that you are adding child.AbsoluteSize.Y to your calculation, which pushes the position to the bottom of the orange frame instead of the top.

Additionally, in Roblox, AbsolutePosition already accounts for the CanvasPosition in real-time. If you add it manually, you are doubling the offset.

local scroll = script.Parent.ScrollingFrame
local child = scroll.Frame2

-- This is the exact screen position
local x = child.AbsolutePosition.X
local y = child.AbsolutePosition.Y

print(x, y)
  1. Remove + child.AbsoluteSize.Y: This was causing the vertical gap seen in your screenshot.
  2. Don’t add CanvasPosition: AbsolutePosition is a screen-space property. As you scroll, the AbsolutePosition of the child updates automatically to reflect where it is on the screen.

Tell me if there’s a misunderstanding.

If i do not add child.AbsoluteSize.Y to the calculation, the position will be to the frame above the target. The small offset will also still be there