In computing, mmap is a POSIX-compliant Unix system call that maps files or devices into memory. It is a method of memory-mapped file I/O. It naturally implements demand paging, because initially file contents are not entirely read from disk and do not use physical RAM at all. The actual reads from disk are performed in "lazy" manner, after a specific location is accessed.

In Linux, Mac OS X and the BSDs, mmap can create several types of mappings.

Anonymous mappings are mappings of that area of the process's virtual memory backed by the swap space instead of by a file in the file system name space. In this respect an anonymous mapping is similar to malloc, and is used in some malloc implementations for certain allocations. However, anonymous mappings are not part of the POSIX standard, though implemented by almost all systems.

File-backed mappings are mappings of virtual memory to files. Access to those areas of memory causes the file to be read. If the mapping is shared, writes to that area in one process will affect other processes with that area mapped and the underlying file; otherwise, if the mapping is private, the changes will not be seen by other processes nor written to the file.

A process reading from or writing to the underlying file will not always see the same data as a process that has mapped the file, since the segment of the file is copied into RAM and periodically flushed to disk. Synchronization can be forced with the msync system call.

mmaping files can significantly reduce memory overhead for applications accessing the same file. If the file is mmaped, the applications can then share the memory area that the file encompasses, instead of loading the file for each application that wants access to it.

Memory shared by mmap is kept visible across a fork.