> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/faqs/more/locksmith-isnt-installing-correctly.md).

# Locksmith isn't installing correctly!

On very rare occasions, Locksmith runs into an issue processing a particular asset in your theme, and can't perfectly complete the installation. If this is happening, Locksmith will let you know within the app, like this:

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/5ddd799f2c7d3a7e9ae472fc/images/5e1cee9b2c7d3a7e9ae625d1/5e1cee2a07975.png)

## If you're confident you don't need Locksmith's code in that asset...

... you can add the asset key to your shop's list of Liquid assets to ignore. You can find this in the "Settings" page of your Locksmith app in the "Advanced" section, and it looks like this:

![](/files/wYR7VEQmMDx9fjQJ5oO8)

Add whatever asset keys you like, making sure to include both the portion before the slash, and the ".liquid" at the end.

## If you're seeing "Asset Template content exceeds 256 KB limit"...

... you may have too many locks and/or keys. We work hard to keep Locksmith trim and efficient, but it *is* possible to exhaust Shopify's size limit for the assets Locksmith uses.

To solve this, remove what locks and keys you can. If you don't see a good way to do so, get in touch – we're happy to help you set up a configuration strategy that covers your bases while staying under the size limit.

## If you're not sure if the problem assets are important or not...

... let us know. Email us at <team@uselocksmith.com>, and we'll help. :) These kinds of things tend to be very, *very* theme-specific, and the best way we can help you is by rolling up our sleeves and going under the hood on your behalf.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.locksmith.guide/faqs/more/locksmith-isnt-installing-correctly.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.