# Runtime Fields

**URL:** <https://discuss.elastic.co/t/runtime-fields/341270>\
**Category:** Elasticsearch\
**Tags:** runtime-fields\
**Created:** [August 21, 2023, 3:01pm UTC](https://discuss.elastic.co/t/runtime-fields/341270 "2023-08-21T15:01:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [August 22, 2023, 2:01pm UTC](https://discuss.elastic.co/t/runtime-fields/341270/2 "2023-08-22T14:01:35Z")

</div>

Hi @MOHIT_SHARMA4,

There is a different in terms of when they are executed. There is a good thread from 2021 [here](https://discuss.elastic.co/t/scripted-fields-vs-runtime-fields/263962) that gives a good explanation of the difference. The [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime.html#runtime-benefits) also gives some benefits of runtime fields here as well.

To determine which one you use I would recommend having a look at the [compromises in the documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime.html#runtime-compromises) for their impact on searching to get an idea of some useful best practices and tradeoffs.

Hope that helps!

---

_[View the full topic](https://discuss.elastic.co/t/runtime-fields/341270)._