CRX id
akbfllpcdehfjdmflobbldkmlnkapocg
akbfllpcdehfjdmflobbldkmlnkapocg
Description from extension meta
Type ;; in any text field to instantly insert today’s date in DD/MM/YYYY HH:MM format - with an optional custom prefix.
Image from store
Description from store
Features:
- ⚡ Fast date insertion — Type ;; and it instantly becomes today's date and time in DD/MM/YYYY HH:MM am/pm format.
- 🎯 Custom trigger — Change the trigger from ;; to anything you want (up to 6 characters).
- 📝 Custom prefix — Add any text before the date (e.g., "Meeting: " or "Done - ") with automatic spacing.
- 🏷️ Custom suffix — Add text after the date and time (e.g., " GMT" or " #TeamUpdate").
- 💡 Smart suffix mode — Type .;; (or . + your trigger) to force include the suffix even when it's disabled.
- 🌐 Works everywhere — Supports input fields, textareas, and contenteditable areas on all websites.
- 🔒 Privacy-first — No ads, no tracking, no data collection.
- ⚙️ Auto-save settings — All preferences sync across your devices automatically.
How it works:
1. Install the extension.
2. Click the toolbar icon to customize your trigger, prefix, and suffix.
3. In any editable field, type your trigger (default: ;;) — it will be replaced with your formatted date and time.
4. Use . + trigger (e.g., .;;) to always include the suffix regardless of settings.
Examples:
Basic usage:
";;" → "18/08/2025 3:45 pm"
With prefix "Meeting: ":
";;" → "Meeting: 18/08/2025 3:45 pm"
With suffix " GMT":
";;" → "18/08/2025 3:45 pm GMT"
Force suffix with dot:
".;;" → "18/08/2025 3:45 pm GMT" (even if suffix is disabled)
Privacy Practices:
This extension does not collect, store, or transmit any personal information, browsing history, or page content.
All processing (detecting the trigger keyword and inserting the date) happens entirely in your browser.
The only saved data is your custom trigger, prefix, and suffix settings, which are stored using Chrome's built-in storage.sync API so they remain available across your devices.
The extension's host permission (<all_urls>) is required solely to allow the content script to detect and replace the trigger keyword in editable fields on any website. No other interaction with the page content occurs.