Two-tool workflow
Prepare timestamp values for URLs
Convert an explicit UTC date to UNIX seconds, use the numeric query value, and verify the date.
Outcome: The date 2024-01-01T00:00:00Z produces 1704067200. A sample query is ?at=1704067200.
Step 1
Convert the date
Select Date to timestamp. Enter 2024-01-01T00:00:00Z. Set Units to Seconds (s) and enable Treat as UTC.
Disable Show parsed datetime for a numeric result. Expect 1704067200. The default enabled option adds readable date text.
Open UNIX Timestamp ConverterStep 2
Check whether encoding changes the value
Enter 1704067200 in Encode mode. Enable Encode all special chars. The result remains 1704067200 because digits need no escaping.
This check is optional. You can use the numeric value directly when the receiving system expects UNIX seconds.
Open URL Encoder and DecoderStep 3
Verify a received value
Select Timestamp to date. Enter 1704067200 and set Units to Seconds (s). Expect Mon 1 January 2024 00:00:00 UTC.
Use the UNIX Timestamp Converter for this check, not URL Decode. Keep the same units in both directions.
Open UNIX Timestamp Converter
Before you finish
Check the result
- Milliseconds (ms) produces 1704067200000 for this date. Do not send milliseconds when an API expects seconds.
- Use an explicit offset or Z. Ambiguous dates can produce an unexpected instant. Inspect the parsed date before use.
- This converter shows the reverse result in UTC. Other applications can display the same instant in a different zone.
- URL encoding preserves query syntax. It does not hide the timestamp.