> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/powershell-commands/new-udhidden.md).

# New-UDHidden

New-UDHidden conditionally hides its child content in PowerShell Universal based on screen size breakpoints like up, down, or only.

### Synopsis

Creates a new hidden element.

### Syntax

```powershell
New-UDHidden [-Id <String>] [-Down <String>] [-Children <ScriptBlock>] [<CommonParameters>]

New-UDHidden [-Id <String>] [-Up <String>] [-Children <ScriptBlock>] [<CommonParameters>]

New-UDHidden [-Id <String>] [-Only <String[]>] [-Children <ScriptBlock>] [<CommonParameters>]
```

### Description

Creates a new hidden element.

### Parameters

#### -Id

The ID of this component. Defaults to a random GUID.

```
Required?                    false
Position?                    named
Default value                [Guid]::NewGuid()
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Down

Content will be hidden at the specified breakpoint.

```
Required?                    false
Position?                    named
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Up

Content will be hidden at the specified breakpoint.

```
Required?                    false
Position?                    named
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Only \<String\[]>

Content will be hidden at the specified breakpoint.

```
Required?                    false
Position?                    named
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### -Children

The content to be hidden.

```
Required?                    false
Position?                    named
Default value
Accept pipeline input?       false
Aliases
Accept wildcard characters?  false
```

#### Common parameters

This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Outputs

### Examples

#### Example 1: Up

```powershell
New-UDHidden -Up md -Content {
    New-UDTypography 'md'
}
```

Content is hidden above the md breakpoint.

#### Example 2: Down

```powershell
New-UDHidden -Down md -Content {
    New-UDTypography 'md'
}
```

Content is hidden below the md breakpoint.

#### Example 3: Only

```powershell
New-UDHidden -Only md -Content {
    New-UDTypography 'md'
}
```

Content is hidden at the md breakpoint.

\[Component("Hidden", "Ghost", "Creates a new hidden element.")]


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell-universal/powershell-commands/new-udhidden.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.