# @timestamp vs timestamp date field

**URL:** <https://discuss.elastic.co/t/timestamp-vs-timestamp-date-field/298483>\
**Category:** Elasticsearch\
**Created:** [March 1, 2022, 8:58am UTC](https://discuss.elastic.co/t/timestamp-vs-timestamp-date-field/298483 "2022-03-01T08:58:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![notgurev](https://avatars.discourse-cdn.com/v4/letter/n/d9b06d/32.png) [@notgurev](https://discuss.elastic.co/u/notgurev)\
**Post date:** [March 1, 2022, 8:58am UTC](https://discuss.elastic.co/t/timestamp-vs-timestamp-date-field/298483/1 "2022-03-01T08:58:43Z")

</div>

Is there any difference between using "@timestamp" and "timestamp" date fields? Does elastic optimize search using those fields across multiple daily indices, perhaps if it knows min and max timestamp for each index?

Currently, I'm using "timestamp", does that hurt my search speed in any way?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 1, 2022, 9:02am UTC](https://discuss.elastic.co/t/timestamp-vs-timestamp-date-field/298483/2 "2022-03-01T09:02:52Z")

</div>

It doesn't matter, as long as it's mapped as a date field.

The former was something that the Stack used as a bit of an internal standard. But it's not a special field.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 29, 2022, 9:03am UTC](https://discuss.elastic.co/t/timestamp-vs-timestamp-date-field/298483/3 "2022-03-29T09:03:08Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.