Input (information, computing, and signals)

Types and examples

Inputs can be organized by their source or form. Common categories include:

• Human-generated: keyboard and mouse actions, voice commands, touch gestures.
• Sensor-generated: temperature readings, camera images, accelerometer signals.
• Programmatic: file contents, network requests, database records, API calls.
• Material or physical: raw materials delivered to an industrial process.

Typical examples in computing are a person typing text into an application, a microphone capturing speech, or a device sending telemetry. For a general reference to the notion of information as input see information.

Characteristics of input

Inputs are commonly described by format (text, binary, analog), modality (visual, auditory, tactile), fidelity (precision and accuracy), timing (continuous, sampled, event-driven), and encoding (how meaning is represented for processing). A program's behavior often depends on input validation, interpretation rules, and quality: corrupted or unexpected input can cause errors or unintended outputs.

History and terminology

The word itself is a straightforward compound in modern English, and its systematic use grew with telecommunications and electronic computing in the twentieth century. In computing contexts, it is often paired with computers and contrasted with output; while input denotes what is provided to a device or program, output denotes what it returns or displays (output).

Uses, importance, and distinctions

Understanding input is central across fields: in engineering it guides control and measurement; in human–computer interaction it shapes interface design; in data science it determines the quality of models. Distinctions to note include input vs instruction (raw data vs commands directing behavior) and input vs feedback (initial data vs responses used to adjust a system). Inputs may be active (deliberate user actions) or passive (ambient sensor readings), and systems often transform inputs through filtering, validation, or normalization before producing results.

Practical considerations

Designers and users must consider accessibility, latency, noise tolerance, and security when handling input. Interfaces should accept a range of valid inputs while rejecting or sanitizing harmful ones. In automated systems, clear specifications for expected input formats reduce ambiguity and improve reliability.