Back
Asciify Logo
Asciify

File Separator

FS (File Separator) is ASCII code point 28 (0x1C), Unicode U+001C. It is a C0 control character that marked the boundary between distinct files or top-level data groups in a serial stream — the highest-level delimiter in ASCII's four-tier separator hierarchy: US (0x1F), RS (0x1E), GS (0x1D), FS (0x1C). On teleprinter and early batch-processing systems, 0x1C let a single tape or transmission carry multiple logical files without requiring external framing. Today it occasionally appears in legacy EDI formats and flat-file data interchange where lightweight record boundaries are preferred over heavier markup. UTF-8 encodes it as the single byte 0x1C; Unicode classifies it as Cc (Control) with the alias FILE SEPARATOR.

Symbol

Technical Details

Code Example

</>
char msg[] = "A\x1CB\x1CC"; // FS (0x1C) separates frames
char *p = msg;
for (int i = 0; i < 3; i++) { char *fs = strchr(p, 0x1C); if (fs) *fs = '\0'; p = fs ? (fs + 1) : p; } // split in-place

Frequently Asked Questions

  • FS (ASCII 28) was designed to separate files or major data sections within a single byte stream. In the hierarchy of ASCII separators, FS is the highest-level delimiter — bigger than Group, Record, or Unit separators.

  • They were the original structured data format. FS/GS/RS/US formed a four-level hierarchy for organizing data — essentially a proto-CSV/JSON system from the 1960s. Modern formats replaced them with visible delimiters, tags, or length-prefixed frames.

  • Because FS is invisible and non-printable — you can't see or type it easily. CSV won because commas are human-readable. Ironically, FS would actually be better technically since it can't appear in normal text, avoiding the quoting nightmare CSVs create.

  • Occasionally. Some data interchange formats, mainframe data exports, and industrial systems still use ASCII separator characters. If you're parsing data and see byte 0x1C, check whether it's being used as a structured delimiter before stripping it.

@workani&@alexluthor
Privacy & legal

Privacy

No accounts, no ads, no tracking cookies, and no cross-site tracking. The only analytics we keep are faceless — anonymous, aggregated counts of pages and searches, never tied to you. We store no IP addresses, set no tracking cookies, and build no profiles. Cloudflare hosts the site and handles requests for delivery and security.

Full privacy policy·Extension privacy·legal@asciify.dev

Attributions & licenses

Twemoji
© Twitter, Inc and other contributors · CC-BY 4.0
Noto Color Emoji
© Google · Apache 2.0
Fluent UI Emoji
© Microsoft · MIT
OpenMoji
© HfG Schwäbisch Gmünd · CC-BY-SA 4.0
Toss Face
© Viva Republica (Toss) · SIL OFL 1.1
JoyPixels
© JoyPixels Inc. · Free Limited Use License
SerenityOS Emoji
© The SerenityOS Developers · BSD-2-Clause
EmojiTwo
© EmojiTwo contributors · CC-BY 4.0
Apple Color Emoji
© Apple, Inc.
Facebook Emoji
© Meta Platforms, Inc.

Apple and Facebook emoji styles are proprietary and shown here solely for reference and comparison — a common-sense application of nominative-use / fair-use principles. asciify is not affiliated with, endorsed by, or sponsored by Apple, Inc., Meta Platforms, Inc., or any other rights holder listed above. If a rights holder requests removal of their emoji style from this site, it will be removed.

All other vendor emoji are reproduced for reference and comparison under their respective open licenses listed above.

Character names and code points from the Unicode® Standard. Unicode® and the Unicode Logo are registered trademarks of Unicode, Inc.

Privacy
© asciify.dev 2025-2026