# Date-only field filter does not match "$NOW" - even after timezone update

**URL:** <https://community.directus.com/t/date-only-field-filter-does-not-match-now-even-after-timezone-update/916>\
**Category:** Help\
**Created:** [August 6, 2025, 5:11am UTC](https://community.directus.com/t/date-only-field-filter-does-not-match-now-even-after-timezone-update/916 "2025-08-06T05:11:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![directus](https://sea2.discourse-cdn.com/flex002/user_avatar/community.directus.com/directus/32/712_2.png) [@directus](https://community.directus.com/u/directus)\
**Post date:** [August 6, 2025, 5:11am UTC](https://community.directus.com/t/date-only-field-filter-does-not-match-now-even-after-timezone-update/916/1 "2025-08-06T05:11:50Z")

</div>

directus: 11.0.0  
have a **date-only** field (`followup`) and in UI I want to filter my collection to show records where the date is **today**.

My server’s timezone (`TZ=Asia/Jerusalem`) is set correctly, and dates display as expected in the UI. When I filter with`$NOW`, no records show up—even though there are records with today’s date. In the relative date display, it says “8 hours ago” (midnight in my timezone), so it seems `$NOW` compares the current timestamp to midnight, which doesn’t match.

**Note:** Manually selecting today’s date in the filter works fine.  
**Question:** How can I reliably filter to show today’s records with a date-only field using`$NOW or any other way`?