> For the complete documentation index, see [llms.txt](https://support.skylum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.skylum.com/missing-fujifilm-camera-profiles.md).

# Missing Fujifilm Camera Profiles

{% hint style="warning" %}
**Note:** Some interface details and visuals in this article may differ from the latest version of Luminar for Desktop. To see the current interface, visit the [Luminar for Desktop walkthrough](https://app.gitbook.com/o/ce1mezuaelhjGQ6S9kTM/s/ynrwC8fnGXULbglwsNaw/~/edit/~/changes/156/how-to-use-luminar-neo/luminar-for-desktop-walkthrough).
{% endhint %}

Luminar for Desktop doesn't include built-in Fujifilm camera profiles (such as Classic Chrome, Velvia, etc.).

Currently, Fujifilm does not publicly provide access to the original film simulation profile data or film simulation LUTs. As a result, authentic Fujifilm film simulations are not currently supported in Luminar for Desktop.

We understand that these profiles are an important part of the post-processing workflow for many Fujifilm photographers. Our team continues to explore possible approaches for broader camera profile support in the future.


---

# 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://support.skylum.com/missing-fujifilm-camera-profiles.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.