> ## Documentation Index
> Fetch the complete documentation index at: https://docs.simular.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# ScreenshotCoordinateType

# Class: ScreenshotCoordinateType

Defined in: [index.d.ts:946](https://github.com/simular-ai/simulang-js-internal/blob/d2b85c3277cbb16ce50c0781e1db8ad2c8a5690e/index.d.ts#L946)

Describes how `(x, y)` coordinates passed to
`Screenshot.toGlobalPhysicalPixels` should be interpreted.

## Constructors

### Constructor

> **new ScreenshotCoordinateType**(): `ScreenshotCoordinateType`

#### Returns

`ScreenshotCoordinateType`

## Methods

### absolute()

> `static` **absolute**(): `ScreenshotCoordinateType`

Defined in: [index.d.ts:951](https://github.com/simular-ai/simulang-js-internal/blob/d2b85c3277cbb16ce50c0781e1db8ad2c8a5690e/index.d.ts#L951)

Coordinates are in screenshot image pixels (valid range:
`0..=image_width-1`).

#### Returns

`ScreenshotCoordinateType`

***

### normalized()

> `static` **normalized**(`range`): `ScreenshotCoordinateType`

Defined in: [index.d.ts:958](https://github.com/simular-ai/simulang-js-internal/blob/d2b85c3277cbb16ce50c0781e1db8ad2c8a5690e/index.d.ts#L958)

Coordinates are normalized to a fixed range. Many VLMs (Qwen-VL,
UI-TARS, etc.) output grounding coordinates in `[0, range]` rather
than in pixel space. `range` specifies the inclusive upper bound
(e.g. 1000, meaning valid coordinates are `0..=1000`).

#### Parameters

##### range

`number`

#### Returns

`ScreenshotCoordinateType`