Local Travel Packing Checklist

How to use Local Travel Packing Checklist

Build your own list with ordinary labelled controls, then check each item as you pack. Add, remove and reorder categories and items without writing JSON. Your choices stay in this tab until you explicitly download them; the tool does not recommend supplies or check physical contents.

1. Enter a title and optional notes, then run to open the local editor. The example loads a fictional complete list; no destination or account is needed.
2. Use Add category and Add item. Enter a name and quantity, edit optional notes, and mark the labelled Packed checkbox. Move and Remove buttons work without dragging; keyboard Tab reaches ordinary controls.
3. Choose A4 or Letter and Printable HTML or Restorable JSON with the fixed buttons. Every edit withdraws the previous download until the current list is validated.
4. Save JSON and select it in a later session to restore current IDs, order, quantities, paper and packed states. For printing, open downloaded HTML and explicitly choose browser Print / Save as PDF; inspect every page.

Good to know

• This is your authored checklist. Packed means you marked an item, not verified physical contents, sufficient supplies or permission to carry anything. There are no destination, weather, airline, visa, health or safety recommendations. Quantities do not calculate weight, volume or baggage allowance.
• Use at most 20 categories and 200 items jointly. Titles, category names and item names have at most 80 UTF-16 units; each notes field has at most 300. Total visible content is at most 20,000 units. A blank title, category name or item name, or a list with no items, leaves all downloads unavailable until corrected.
• Quantities are canonical string values from "1" to "999". Numeric JSON values, decimals, exponents, leading zeros and coercible arrays refuse. Packed values must be exact booleans. Imported category/item IDs must be unique ASCII local identifiers across the whole list.
• Imports accept only tooljovia.packing-checklist.v1 JSON, not arbitrary task, spreadsheet or travel app formats. Files are 1–150,000 UTF-8 bytes, source is at most 50,000 UTF-16 units, with one optional initial BOM, at most 3,000 values and 8 nested levels. Duplicate/unknown members, invalid UTF-8, unsupported controls and malformed Unicode refuse atomically; the file read has a 5-second deadline.
• Current JSON preserves all current content, paper and item state. Raw imports, source filenames, removed entries and old edits are not hidden in exports. Nothing is automatically saved. Downloaded JSON and HTML still contain your current personal text; inspect them before sharing.
• HTML is a complete scriptless document with original fixed CSS, literal source text, no active links, remote resources or user HTML/CSS. Packed status appears as readable text as well as a mark. HTML is capped at 250,000 UTF-16 units and UTF-8 bytes; JSON at 50,000 UTF-16 units and 150,000 UTF-8 bytes so every saved file fits the same import profile. An oversized complete export refuses rather than dropping items.
• The app does not encode PDF or print automatically. Browser Print / Save as PDF, line breaks, fonts and physical printer settings are outside the data model; no page-count or identical-print guarantee is made. Reset, another run and pagehide dispose the editor and cancel its pending animation frame. Processing uses no upload, account, persistence or personal-content analytics.