YouTube Chapter & Timestamp Builder

Choose the output and identify the video version

Choose YouTube mode for a plain timestamp-and-title description list. Choose linked moments for selected start-at links to one YouTube video. These are different jobs: a description list maps the whole recording, while a sharing list can contain just the useful moments. Switching the output does not discover missing topics or change what happened in the video.

Give the project a recognizable name, such as Workshop setup, final edit, to distinguish its downloads. Use notes for a handoff reminder about the version and remaining checks. A project title can contain up to 80 characters; notes allow 600 characters across twelve lines. Keep longer production documentation separately rather than hiding it inside chapter titles.

Enter the finished video length when you know it. The tool uses that value as the endpoint for the last segment and to identify starts that reach or pass the end. A length copied from an earlier edit can make correct-looking arithmetic describe the wrong recording. Confirm that any removed introduction, added sponsor message, or changed closing sequence is already reflected in both your timestamp notes and the duration.

A YouTube URL is optional for the plain chapter list and required for linked moments. It identifies the destination; it does not load, embed, or inspect the remote video. Supported HTTPS watch, short-link, and live-video URL forms are checked for a valid video identifier. Exported links use a clean watch address with the chosen integer start time, removing previous time and tracking values rather than carrying an old destination offset forward.

Enter one editable source list with meaningful titles

Write one marker per line, with a time token, a space, and a nonempty title. For example, 2:10 Run the first task pairs a start with its purpose. The accepted time forms are M:SS and H:MM:SS; seconds must stay between 00 and 59, and the middle field in the three-part form follows the same range. Decimal seconds and bare second counts are not timestamp tokens here.

Paste working notes directly into the source field, then read every flagged line. The review updates from this single list, so there is no separate hidden set of markers that can drift away from the text you are editing. Blank lines remain part of the saved source but do not count as chapters. A line containing a heading without a time is not silently treated as a chapter or quietly discarded.

Use a title that identifies the destination. Replace Important bit with a concrete phrase such as Set the workspace folder. The tool checks whether a title exists and fits its 120-character budget, not whether its promise is true. Compare the words with the recording: a fluent title can mislead even when the timing is valid and the export is available.

The builder accepts up to 100 markers, 300 source lines, 20,000 source characters, and 64 KiB of UTF-8 source text. These are its own processing budgets, not statements about YouTube’s native chapter limits. If a large paste exceeds them, reduce the working material deliberately. Do not export the first portion as though the omitted notes had been reviewed. Keep the original elsewhere before condensing a long production outline into viewer-facing navigation.

Work through the complete six-minute example

Load the fictional six-minute YouTube example. Its complete list is 0:00 Introduction, 0:30 Set up the workspace, 2:10 Run the first task, and 4:20 Review the result, with a duration of 6:00. Each item is a start, not an endpoint. The next item closes the current segment; the supplied duration closes the last. Do not add a chapter marker at 6:00.

Convert the times into seconds before subtracting. The four starts are 0, 30, 130, and 260 seconds, and the end is 360 seconds. Introduction therefore lasts 30 minus 0, or 30 seconds. Set up the workspace lasts 130 minus 30, or 100 seconds. Run the first task lasts 260 minus 130, or 130 seconds. Review the result lasts 360 minus 260, or 100 seconds. Each subtraction uses neighboring boundaries.

The segments are therefore 30, 100, 130, and 100 seconds. Adding them gives 360 seconds, exactly six minutes. Written as elapsed spans, they are 0:30, 1:40, 2:10, and 1:40. Notice that a start of 2:10 does not mean the second segment lasts two minutes ten seconds. Confusing a position with a length is an easy way to approve the wrong calculation when reviewing chapter notes by eye.

All four starts increase, the list begins at zero, and every segment in this example is longer than ten seconds. Remove the duration and the first three lengths remain calculable, but the final length becomes unknown. Change the end to 4:25 and the last segment becomes five seconds, requiring attention in YouTube mode. Change it to 4:20 and the final marker reaches the end rather than opening a usable segment. These changes illustrate why the endpoint matters.

Read errors, warnings, and lengths as different evidence

An error means something prevents the complete list from being output-ready under the selected mode. Examples include an unreadable time, an empty title, duplicate starts, or a start that follows a later marker in the source. Correct the actual cause, then review the updated result. A row may be individually understandable while the whole project still has errors. That row is useful for diagnosis, not permission to copy a partial list as the finished result.

An unknown-end warning is different from a failed calculation. Without a duration, the builder can still calculate gaps between known starts, but it cannot determine the final span. A list may be copyable with that warning; it is not a guarantee that the last chapter meets the intended length. Supply a trustworthy duration or record the remaining end check in the handoff. Do not substitute a convenient estimate simply to remove the warning.

Segment lengths describe your supplied boundaries, not audience retention, pacing quality, or how much explanation a subject deserves. A two-minute demonstration can be appropriate, while a thirty-second summary can contain too many unrelated ideas. Use the lengths to spot candidates for review, then listen or watch. The timeline cannot tell whether a title begins halfway through a sentence, whether a warning belongs before the action, or whether the viewer needs an earlier setup step.

The tool’s 24-hour time ceiling is another local processing limit. Passing checks does not verify video existence, viewer access, or native chapter availability. Keep three judgments separate: the text can be parsed, the supplied timing satisfies the selected checks, and the real viewer journey works. The builder helps with the first two using your input. Testing the published destination remains your responsibility.

Sort deliberately without losing unresolved entries

Viewing notes often arrive in discovery order rather than playback order. You might paste 4:20 first, then add an earlier setup note after a second review. Use the deliberate sort-and-format action once every source line has a readable time and title. It orders the complete marker set by start and gives times a consistent format. Review the changed list afterward, because chronological order alone cannot establish whether each label describes the correct moment.

Sorting cannot guess what broken syntax means. A line such as 2:70 Check the result needs correction before sorting can proceed. Do not assume it means 3:10: it could be a mistyped 2:10 or a note from another cut. The transaction leaves your source intact when it cannot format every entry, protecting the connection between the original material and the review you send.

Equal times remain visible after sorting. If two lines both start at 2:10, decide whether they describe one combined topic, whether one belongs later, or whether one is an accidental duplicate. The tool does not choose a winner and delete the other title. Merge wording only after checking the recording. Moving a duplicate forward by an arbitrary second can hide the collision while creating an inaccurate boundary or an unnecessarily short neighboring segment.

Formatting makes positions below one hour look like 2:10 and positions at or above one hour look like 1:02:10. It does not retime an edited video or translate old source notes into a new cut. After any deliberate sort, compare the marker count, opening item, and closing item with your intended outline. Then check transitions that were moved far through the list; a timestamp pasted with the wrong title can remain perfectly sortable.

Mark a local video while keeping the naming decision yours

The optional local-video workspace lets you play a file through your browser’s native video controls and mark its current position. No file upload is involved. Use the final local export when possible, then pause near a real change of task or subject. Marking appends a human-editable placeholder such as Chapter 3. Replace that label with your own description before handoff. The player does not listen for topics, identify speakers, or generate an interpretation of the footage.

Marks use complete seconds by flooring the current position, never rounding forward. At a reported playback position of 130.9 seconds, the appended start is 130 seconds, displayed as 2:10. Replay the transition to decide whether that second is a useful entry point. Browser playback is not a frame-accurate editing timeline, so a marker should be treated as a reviewable navigation boundary rather than an exact cut instruction for an editor.

A local candidate must fit the builder’s limits: 150 MiB, a positive finite duration no longer than 24 hours, no side above 4096 pixels, and no more than 9,437,184 pixels in a frame. Playback also depends on the browser’s available decoder. A familiar filename extension does not guarantee compatibility. If a candidate is refused, the previously accepted video and project remain in place; check which recording is active before adding another marker.

Loading media does not silently replace your entered duration. Use the explicit video-length action when that file is the right source; it floors the length to complete seconds too. A file shorter than one second cannot provide a positive integer duration. Save the editable project before leaving, but retain the video separately: neither its bytes nor its filename is included in project JSON, and reopening that project does not restore a media attachment.

Choose an export that matches the handoff

Copy the list or download TXT when the complete output is ready and you need plain text for a description or sharing draft. These actions are not shortcuts around unresolved errors. If any line prevents readiness, the builder withholds the final list rather than presenting only the valid rows. Review warnings before using a copyable result, especially an unknown ending. The recipient should know what remains unverified even when the text itself can be exported.

Use the CSV review for a structured inspection of settings, source records, marker calculations, and issues. It keeps the full raw input instead of turning a broken line into missing evidence. This is helpful when a collaborator needs to trace an error back to the exact note that caused it. CSV is a review export, not an automatic YouTube import file. Its values are selectable, making it useful for checking boundaries in another working document.

The PDF provides a styled review with the complete source, settings, records, issues, notes, and method. It can document an unfinished project, but it is not an output-ready list when errors remain. The PDF is rasterized; choose CSV or JSON for selectable data. Use the report to explain decisions such as combining duplicate starts, rather than leaving a collaborator to interpret an isolated timeline.

Save JSON for continued editing. It preserves the supported project text and settings, including notes, without bundling the video. Imports follow a strict project schema and a 128 KiB file budget; an invalid project is refused rather than partly applied. There is no autosave. Keep a saved version before changing source recordings or replacing a long outline. Your inputs are not placed in page URLs or private-input analytics, although ordinary site analytics can still run.

Apply the reviewed list and test the real destination

For manual YouTube chapters, the practical baseline is a first timestamp at 00:00, at least three ascending starts, and chapter spans of at least ten seconds. The builder’s canonical 0:00 represents that zero start. Copy the reviewed description list into the intended video’s description and save there yourself. Native availability, Advanced features access, and processing are separate checks the tool cannot verify. Automatic chapters are a different YouTube feature, not content created by this builder.

Check the saved video as a viewer. Open the beginning, a middle transition, and the final chapter, and compare the actual arrival point with the title. If something appears wrong, confirm the saved text and source version before changing multiple variables. A good local review cannot detect an unpublished description edit or an inaccessible destination. Keep the review report as the record of what was prepared, not proof of what the live player currently displays.

For selected sharing moments, use linked mode rather than expecting description-mode checks to fit a shortened list. Keep the full navigation project separately, then curate moments answering a specific question. Find related preparation tools in the free tools directory. A clear list aids navigation; it is not a ranking promise, a search-performance measurement, or evidence that every visitor will watch longer.

When the chapter handoff is finished, recurring account interaction is a separate job. SMTasker’s YouTube tools support viewing, likes, prepared comments, and subscriptions through connected Android phones managed from Windows or macOS. You can evaluate a focused comment routine during the five-day trial. Keep its targets and review separate from chapter preparation: the app does not upload your video, set its chapters, or import this browser project into a publishing workflow.

Questions about video chapters and timestamps