> For the complete documentation index, see [llms.txt](https://cbwire.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cbwire.ortusbooks.com/template-directives/wire-cloak.md).

# wire:cloak

`wire:cloak` is a directive that hides elements on page load until Livewire is fully initialized. This is useful for preventing the "flash of unstyled content" that can occur when the page loads before Livewire has a chance to initialize.

## Basic Usage

To use `wire:cloak`, add the directive to any element you want to hide during page load:

```html
<div wire:cloak>
    This content will be hidden until Livewire is fully loaded
</div>
```

## Dynamic Content

`wire:cloak` is particularly useful in scenarios where you want to prevent users from seeing uninitialized dynamic content such as elements shown or hidden using `wire:show`.

{% tabs %}
{% tab title="BoxLang" %}

```html
<!-- wires/togglePanel.bxm -->
<bx:output>
<div>
    <div wire:show="expanded" wire:cloak>
        <!-- Chevron down icon... -->
    </div>

    <div wire:show="!expanded" wire:cloak>
        <!-- Chevron right icon... -->
    </div>
</div>
</bx:output>
```

{% endtab %}

{% tab title="CFML" %}

```html
<!-- wires/togglePanel.cfm -->
<cfoutput>
<div>
    <div wire:show="expanded" wire:cloak>
        <!-- Chevron down icon... -->
    </div>

    <div wire:show="!expanded" wire:cloak>
        <!-- Chevron right icon... -->
    </div>
</div>
</cfoutput>
```

{% endtab %}
{% endtabs %}

In the above example, without `wire:cloak`, both icons would be shown before Livewire initializes. However, with `wire:cloak`, both elements will be hidden until initialization.


---

# 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://cbwire.ortusbooks.com/template-directives/wire-cloak.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.
