> For the complete documentation index, see [llms.txt](https://docs.fylr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fylr.io/for-system-administrators/symptom-and-solution/blurred-preview-images-only.md).

# blurred preview images only

<figure><img src="/files/W1nJy64KGO8NOSjQBue1" alt=""><figcaption></figcaption></figure>

## Background knowledge

1. Blurred previews can be displayed from the SQL database without needing any access to the actual asset images or asset previews. Whenever there is a problem accessing preview images, fylr falls back to just showing the blurred previews from the tiny "blur hash" saved in SQL database.
2. In fylr, assets and previews are strongly linked to the URL. So if you change fylr's URL, only blurred previews are available. This can be remedied with a re-index, which updates the URL associated with assets and their previews.

## Possible causes:

* You changed the URL, for example http instead https or vice versa, or you changed the domain name in fylr's `externalURL` setting. This can be remedied with a re-index (which will take time)
* There is a routing or firewalling problem so that asset previews cannot be shown. This would be additionally indicated by error messages in ...
  * in your browsers development tools (errors in "console" of "dev-tools" visibel with the `F12` key)
  * or in error messages in the fylr log (accessible as fylr output or container output on the sysadmin level, or in <https://your-fylr.example.co&#x6D;**/inspect/system/console/>\*\* (needs fylr root account access).<br>


---

# 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://docs.fylr.io/for-system-administrators/symptom-and-solution/blurred-preview-images-only.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.