> 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/help/tutorials/for-administrators/search-text-in-images-or-office-files.md).

# Search in Text of Images or Office Files

{% hint style="warning" %}
Large files / large amount of files may temporarily slow down your instance due to increased processing requirements.

Some OCR jobs may fail to produce correct output because of source quality (fonts, external artifacts, DPI).

Special characters, pages structures and editorial features (tables, headers, footnotes etc.) are not filtered and may produce nonsensical contents.
{% endhint %}

By default, OCR is disabled for all files. This tutorial will expand on adding file types.

1. Navigate to [Base Configuration](/for-administrators/readme.md), into the [File Worker](/for-administrators/readme/file-worker.md)
2. Uncheck "Use Default Settings"
3. Expand "CUSTOM METADATA"
4. Add the extensions you want OCR applied to and written to the index

<figure><img src="/files/JDqY9okMR5y79JPALak7" alt="" width="563"><figcaption><p>Example configuration of OCR to include JP(E)G, PNG, EPUB, PDF</p></figcaption></figure>

The recipe configuration offers more options, those are not necessarily required to run OCR on new files.

### Verify OCR is Working

* Create a new record using the plus-icon
* As soon as you save, the OCR is beginning
* Locate the newly created record and open in detail view

<figure><img src="/files/ERTZHmZNmvSFUrFkfv30" alt=""><figcaption><p>fylr detail view of example record</p></figcaption></figure>

* Use the "Info" button to access the data available in index
* In the "Advanced" tab, you will find the indexed content of the file under "\_fulltext"

<figure><img src="/files/Zym4RDnBVKZQBS76K1Hq" alt=""><figcaption><p>Info section of a fylr record displaying the indexed OCR output</p></figcaption></figure>

To search for the extracted content, make sure that the OCR-recognizable text of your files is included in the search result by activating the checkbox in the 3-dot menu on the far right of the search bar.

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

Now you can find records by searching the human readable content of files - just type in the search bar as usual.

### Applying OCR on Already Existing Records

OCR image-to-text will run when indexing a file. Consult [Regenerating preview images](/help/tutorials/for-system-administrators/regenerating-preview-images.md) for a tutorial on how to reindex one or more existing records.


---

# 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/help/tutorials/for-administrators/search-text-in-images-or-office-files.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.