Resume Point vs. Bookmark: Two Different Saved States
A resume point supports continuation from current progress; a bookmark preserves a chosen reference and may outlive later playback updates.
In short: A resume point is usually the current saved place from which playback can continue. A bookmark is a deliberate or system-created reference to an item or moment that can remain even after playback moves elsewhere. Products may use different names and may not offer bookmarks at all, so verify the visible feature before applying either term.
Both states can refer to time, but their jobs differ. Calling a resume point a bookmark can make support evidence ambiguous: did playback fail to continue, or did a saved reference disappear?
The media player glossary defines the surrounding position, completion, favorite, and history concepts.
A resume point follows current progress
A resume point is commonly updated when playback advances and the session exits or periodically saves state. A later session can use it to continue near that position. A player may round, debounce, or slightly adjust the point.
The current playback time exposed by a media engine is not automatically the same as a service-side saved resume point. Saving and synchronization are additional product behaviors.
A bookmark preserves a reference
A bookmark is typically created to remember an item or a moment. It may be explicit, such as a user selecting "save," or generated by a defined workflow. Multiple bookmarks can exist for one item in systems designed that way.
Do not assume Norva currently exposes moment bookmarks. This article explains the generic distinction; all product claims require current official verification.
Creation differs
Resume points are often created as a consequence of ordinary playback. Bookmarks generally require an intentional save action or a clearly defined automated rule. If no bookmark control is visible, do not describe a favorite, history row, or progress bar as one.
Record the exact label and action used in the interface when reporting a problem.
Update behavior differs
New playback commonly replaces or advances a resume point. A bookmark should remain stable until edited or removed according to the product's model. Seeking past a bookmark does not necessarily move it.
The position versus completion guide shows why a resume point can also behave differently after an item is considered completed.
Playback effects differ
Opening an item with a resume point may offer or automatically use that point. Selecting a bookmark may jump to a saved moment, open details, or simply identify an item. These are interface-specific choices.
Never infer actual playback from a static marker. Record the displayed reference and the position that playback reaches.
Scope and synchronization differ
Either state may belong to an account, profile, item version, or device, depending on the service. A resume point attached to one profile should not be compared with another profile's state. A bookmark may be personal, shared, local, or synchronized.
Norva can keep playback progress across supported devices under the same account. That supported progress behavior does not establish a separate bookmark capability.
Privacy implications differ
A resume point can reveal that an item was opened and approximately how far it was watched. A bookmark can reveal deliberate interest in a particular item or moment. Both should be treated as viewing-context data when screens, exports, or support evidence are shared.
Use neutral item codes and approximate positions in a troubleshooting record.
Test the state you actually have
For resume behavior, play a known item to a distinctive point, exit normally, and inspect displayed and actual resume positions on the same screen and profile. For a visible bookmark feature, create one through the labeled control, advance playback elsewhere, and verify whether the reference remains.
Compare the result with manual progress tracking if the desired saved-reference workflow is not supported.
Original evidence: saved-state matrix
| Dimension | Resume point | Bookmark |
|---|---|---|
| Primary purpose | Continue current viewing | Preserve a chosen reference |
| Typical creation | Ordinary playback save | Explicit or defined save action |
| Typical quantity | Often one current point per context | May allow multiple references |
| Update trigger | Playback advances | User or rule edits reference |
| Playback effect | Offer or use continuation | Product-specific jump or reference |
| Completion interaction | May reset or disappear | May remain independent |
| Privacy meaning | Viewing extent | Deliberate saved interest |
| Product availability | Common but conditional | Must be verified |
Common terminology mistakes
- Calling every progress marker a bookmark.
- Treating a favorite as a saved timestamp.
- Assuming a bookmark feature exists without a visible control.
- Comparing states across different profiles or versions.
- Inferring playback position from a static icon.
- Sharing precise private viewing moments unnecessarily.
Frequently asked questions
Is a favorite the same as a bookmark?
Not necessarily. A favorite usually marks an item for discovery, while a moment bookmark refers to an item or position. Use the product's actual labels.
Can a resume point survive completion?
It may, depending on the product's completion and resume rules. Inspect position, completion, and actual opening behavior separately.
Does Norva offer moment bookmarks?
No claim should be made here. Verify current official features and the visible interface. Norva's documented progress capability should not be relabeled as a bookmark feature.