A timestamp identifies a position in a video. The accepted syntax and units depend on the API field or editing tool. Check that field’s reference before sending a value; the examples below are conversions, not a promise that every Picsart endpoint accepts every notation.
Common representations
HH:MM:SS: hours, minutes and seconds.01:20:10represents 4,810 seconds.MM:SS: minutes and seconds, if the field defines that notation.04:03represents 243 seconds.HH:MM:SS.mmm: adds a fractional second.00:02:00.200represents 120.2 seconds.- Plain seconds:
120or120.2, where the field accepts a numeric duration. - Milliseconds and microseconds: 1,200 milliseconds = 1.2 seconds; 1,300 microseconds = 0.0013 seconds. Only add suffixes such as
msorusif the field explicitly permits them.
Convert consistently
Seconds = hours × 3,600 + minutes × 60 + seconds. Divide milliseconds by 1,000, or microseconds by 1,000,000, to obtain seconds. To convert seconds back, take whole hours first, then whole minutes from the remainder, then the remaining seconds.
Keep adequate precision during calculations and round only when the destination requires it. A decimal fraction such as .2 is two-tenths of a second; writing .200 does not change its value.
Frames and timecode
Frame numbers are useful when the workflow requires them, but conversion to elapsed time needs the frame rate and timecode convention. Do not assume a fixed rate for variable-frame-rate media or treat a frame count as milliseconds.
If a trim or seek lands in the wrong place
- Confirm whether the field expects a start position, end position or duration.
- Check the unit, separator, numeric/string type and allowed precision.
- Verify that the requested range lies within the input duration.
- Preview the exported clip and compare both start and end; decoding and frame boundaries can affect where an operation lands.