# Set unread marker for a chat to a given message **URL:** \ **Category:** Feature Proposal\ **Tags:** user-interface\ **Created:** [October 4, 2026, 6:31am UTC](https://support.delta.chat/t/set-unread-marker-for-a-chat-to-a-given-message/5867 "2026-10-04T06:31:27Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ian](https://support.delta.chat/user_avatar/support.delta.chat/ian/32/3164_2.png) [@ian](https://support.delta.chat/u/ian)\ **Post date:** [October 4, 2026, 6:31am UTC](https://support.delta.chat/t/set-unread-marker-for-a-chat-to-a-given-message/5867/1 "2026-10-04T06:31:27Z")
I would like to click on the … further actions button on a single message and select mark unread from here, and it would reset the unread marker to that message, close the chat and mark the chat as unread. I would then have the opportunity to continue reading the chat from **that** point on when I return later by clicking jump to unread. As a continuation of: > [@Mark messages as unread](https://support.delta.chat/t/mark-messages-as-unread/4077/17): > > I’d say almost. The title of the issue implies something else: “Mark messages as unread”. To implement this feature, you would have to click … on a single message and select unread, and it would reset the unread marker to that message, close the chat and mark the chat as unread. You would then have the opportunity to continue reading from that point on. The body of the issue did not describe this sufficiently. Should I open a separate one about this then? ---
**Author:** ![WofWca](https://support.delta.chat/user_avatar/support.delta.chat/wofwca/32/1702_2.png) [@WofWca](https://support.delta.chat/u/WofWca)\ **Post date:** [October 4, 2026, 9:34am UTC](https://support.delta.chat/t/set-unread-marker-for-a-chat-to-a-given-message/5867/2 "2026-10-04T09:34:07Z")
Would [Continue where I stayed in the chat (remember scroll position)](https://support.delta.chat/t/continue-where-i-stayed-in-the-chat-remember-scroll-position/554) not completely cover the use case? ---
**Author:** ![r10s](https://support.delta.chat/user_avatar/support.delta.chat/r10s/32/1513_2.png) [@r10s](https://support.delta.chat/u/r10s)\ **Post date:** [October 4, 2026, 9:59am UTC](https://support.delta.chat/t/set-unread-marker-for-a-chat-to-a-given-message/5867/3 "2026-10-04T09:59:18Z")
it would help probably, but the idea of @ian seems to be that you can have read a chat fully, and then later, for any message, mark the thread unread from any point. if you re-enter the chat, you read message from there on. while that may be helpful for some, it is not really a thing for the many. it is a too nerdy and too hidden feature for the average user we want to target and for what we’re usually doing in Delta Chat. also, it turns the very temporary unread counter into smth you start fine-tweaking from the user side on. but: it is kind of a bookmark, you can already do that today by saving a message and tap the “go to message” button - that reminder not disappear by accidentally entering, and you even can have several of them per chat: ![Screenshot 2026-10-04 at 11.55.30](https://support.delta.chat/uploads/default/original/2X/0/0f74f13bb2698957b610103d7106c9601b53334f.png) ---
**Author:** ![WofWca](https://support.delta.chat/user_avatar/support.delta.chat/wofwca/32/1702_2.png) [@WofWca](https://support.delta.chat/u/WofWca)\ **Post date:** [October 4, 2026, 10:01am UTC](https://support.delta.chat/t/set-unread-marker-for-a-chat-to-a-given-message/5867/4 "2026-10-04T10:01:41Z")
> [@r10s](#): > > you can have read a chat fully, and then later, for any message, mark the thread unread from any point. if you re-enter the chat, you read message from there on. I’m not seeing how this is different from keeping the scroll position + marking the chat as unread. ---
**Author:** ![r10s](https://support.delta.chat/user_avatar/support.delta.chat/r10s/32/1513_2.png) [@r10s](https://support.delta.chat/u/r10s)\ **Post date:** [October 4, 2026, 10:10am UTC](https://support.delta.chat/t/set-unread-marker-for-a-chat-to-a-given-message/5867/5 "2026-10-04T10:10:45Z")
ah, sorry, i mixed that with the actually wanted and actionable item of only marking actually read messages as unread (and not the whole chat): > > > the current approach to chat read status synchronization has several flaws: > > \- w…hen user opens a chat in device A, the chat loses the badge counter, but on device B only the messages that got seen in device A get deducted from the counter, here there is already a split in chat status synchronization > \- when user enters a chat and read only the messages shown in the screen, then go out, then the chat counter is lost and user end at the end of the chat without possibility to continue reading where they left > > the solution: > > I already talked a bit about this with @link2xt, a simple solution is: > > When receiving a "message was marked as read" event, instead of just removing that message from the badge counter, consider "noticed" ALL previous messages ABOVE that message id > > when opening a chat, don't mark it as notice, this API could probably just be deleted, then the "current chat position" marker will always be at the last seen/read message and user can re-enter the chat and continue > > when the user uses the "go to bottom" button, then the latest messages in the chat are marked as seen then in the other devices the badge counter will disappear even if there were unread messages that were skipped by jumping to bottom, solving the current problem of unwanted "random skipped messages" still counting in the badge counter and having badge counter in one device while not in another ftr, in contrast “remembering scroll position” is nothing agreed on nor actionable, it is not what most user seem to expect, and there is low interest otherwise ---
**Author:** ![ian](https://support.delta.chat/user_avatar/support.delta.chat/ian/32/3164_2.png) [@ian](https://support.delta.chat/u/ian)\ **Post date:** [October 4, 2026, 6:04pm UTC](https://support.delta.chat/t/set-unread-marker-for-a-chat-to-a-given-message/5867/6 "2026-10-04T18:04:29Z")
Yes, it happens often in high traffic groups that if I only have a few minutes, I couldn’t scroll to the end before I have to close the app and would like to continue where I left off. The “geeky” use case is about quickly scrolling past the chat given a few minutes of free time to see whether there are anything urgent or actionable mentioned. If yes, note it done or do it, if no, scroll back and then read everything thoroughly when I next have time.