Files and Burs

§1Rows of tiny teeth

A file is a hardened steel blade covered in many small teeth, each a miniature cutting edge. Drawn across the work, the teeth shave off fine chips — the same wedge-and-chip action as any cutting tool, multiplied over hundreds of edges.

What makes the file special is control, not power: hundreds of tiny edges each take so little that the operator can remove metal a whisker at a time, feeling and steering the cut by hand. That suits the jobs machines struggle with — breaking a sharp edge, fitting one part to another, dressing a weld, finishing a curve, deburring. The same principle, spun rather than stroked, gives the rotary bur (§6) for powered hand work in a die grinder. Both are governed by the same three things this page covers: the tooth pattern (§2), the coarseness (§3), and the hardness that lets the teeth cut at all (§4).

Contents

§2Single-cut and double-cut

Files carry their teeth in one of two patterns, and the choice sets whether the file cuts fast or finishes fine (the hero).

A single-cut file has one set of parallel rows of teeth running diagonally across its face; it removes metal more slowly but leaves a smoother surface, and is used for finishing, for sharpening edges, and on harder materials. A double-cut file adds a second set of rows crossing the first, breaking the teeth into a field of individual sharp points; it cuts much faster because each point acts alone, but leaves a rougher surface, so it is the choice for rapid stock removal on softer metals. The rule is simple: double-cut to take metal off quickly, single-cut to finish. Curved-tooth and rasp patterns extend the family for soft materials and bodywork, but the single/double distinction covers the common engineering files.

Contents

§3Coarseness grades

Independently of the cut pattern, files are graded by how closely the teeth are spaced — their coarseness — from coarse to fine.

The common coarseness grades, coarse to fine
Grade	Teeth spacing	Use
Rough / coarse	widely spaced	heavy, fast removal on soft metal
Bastard	medium-coarse	general rough work — the usual first file
Second-cut	medium	intermediate shaping and truing
Smooth	fine	finishing to size and surface
Dead-smooth	very fine	final finish
The teeth also grow finer, at a given grade, as the file gets shorter, so grade is relative to length. The working sequence mirrors machining — start with a bastard to bring the work close, move to second-cut to true it, and finish with a smooth file to size — the coarse file for speed, the fine file for finish, exactly as roughing precedes finishing on a machine.

Contents

§4Harder than the work

A file cuts steel because it is harder than the steel it cuts — hardened to around 64 on the Rockwell C scale, near the top of what steel reaches.

The materials section set out the rule that a cutting tool must be markedly harder than its work, and the file is a pure case: file teeth are hardened to roughly HRC 64, well above the HRC 20–30 of the mild steel and the softer metals a file is used on, so the teeth bite in rather than skate off. The corollary is a real limitation — a file cannot cut anything approaching its own hardness, so hardened steel simply glazes or ruins a file, and such work must go to a grinding wheel (an abrasive harder still) instead. It also means files are brittle: that same high hardness makes them snap if bent or dropped, so a file is never used as a lever or pry bar. Hard enough to cut soft steel, too hard and brittle to survive misuse or to touch hardened work.

Contents

§5Filing technique

A file cuts on the forward stroke only, and using it well is a matter of stroke, pressure and keeping the teeth clear.

The teeth point forward, so the file cuts as it is pushed and should be lifted, or at least unloaded, on the return — dragging it back under pressure only dulls the teeth. Cross-filing, pushing across the work for stock removal, is followed by draw-filing, drawing a smooth file sideways along the work, for a fine, straight finish. Pressure is applied on the push and eased on the return. And the teeth must be kept clean: soft metals, especially aluminium and lead, clog the teeth (“pinning”), and the trapped chips then scratch the work, so the file is cleared with a file card (a wire brush) and, for sticky metals, rubbed with chalk to stop the pins forming. Stroke forward, finish by draw-filing, and keep the teeth clear — the whole craft of the file in three habits.

Contents

§6Rotary burs

A rotary bur is a small toothed cutter spun at high speed in a die grinder — the powered equivalent of a file for shaping, deburring and blending in awkward places.

Example 1 — bur speed

Burs run fast — commonly 15 000 to 35 000 rev/min — and because they are small, even those high speeds give a modest rim speed. A 6 mm carbide bur at 25 000 rev/min has a rim speed of π × 6 × 25 000 ÷ 60 000 = 7.85 m/s; a smaller 3 mm bur must spin faster to cut well, reaching about 4.71 m/s even at 30 000 rev/min. The lesson from the same N = 1000 V/(π D) relationship used throughout machining is that small tools need very high spindle speeds to reach a useful cutting speed — which is why die grinders spin so fast. Carbide burs cut steel and cast iron; high-speed-steel burs suit softer metals; and the right speed keeps the bur cutting cleanly rather than rubbing and glazing.

Contents

§7Quick reference

The working core of the page on one card rack.

Cut pattern

single-cut → finish

double-cut → fast removal

Coarseness

bastard → second-cut → smooth

Hardness

teeth ~HRC 64

can't cut hardened steel

Technique

cuts on push · draw-file to finish

clear pinning with a card

Burs

15 000–35 000 rev/min

6 mm @ 25 000 → 7.85 m/s

Contents

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Files and Burs. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to carry the subject from function and assumptions through design evidence, verification and controlled release. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Apply Files and Burs by beginning with the duty, not the component or software command. Convert the key ideas—burs, rotary, files, double-cut, coarseness—into measurable requirements and interfaces. Record operating and non-operating environments, duty cycle, expected life, loads, energy sources, human interaction and reasonably foreseeable abnormal conditions. When a value is not a project requirement or verified supplier datum, identify it as an assumption or illustrative value.

Create a calculation and evidence trail that another competent person can audit. Every input should carry a source, unit, revision and uncertainty or tolerance where relevant. Every model should state its boundary conditions and limitations. Keep nominal capacity separate from design capacity, and keep verification margin separate from an arbitrary safety factor. If a code or standard governs the work, confirm the applicable edition and contractual status rather than copying a number from a secondary summary.

Design for manufacture, assembly, inspection, operation and maintenance at the same time. A technically valid geometry can still fail because it cannot be fixtured, measured, cleaned, guarded, reached or replaced. Review process capability, datum or reference strategy, tolerance accumulation, access, error-proofing and changeover. Where people interact with plant, apply the hierarchy of controls and consult those who will operate, clean, maintain and recover the equipment.

Plan verification before release. Define the characteristic, method, equipment, sample or test condition, acceptance criterion, record and responsible person. Validation then asks a different question: whether the resulting system is effective and suitable in the intended use context. A passed drawing check or analysis does not by itself validate usability, maintainability or production performance.

Step-by-step operating method

Define the duty. Capture the required function, interfaces, operating environment, life, loads and unacceptable outcomes.
Establish the model. Identify governing principles, units, material or process data, assumptions and uncertainty.
Develop alternatives. Compare feasible concepts against performance, manufacturability, safety, maintainability and cost.
Verify the design. Use analysis, test, inspection or demonstration with acceptance criteria defined before execution.
Release and learn. Baseline the design, control changes, retain evidence and feed operating results into the next revision.

Illustrative design review record

Illustrative values only. Build a one-page record with the required function, input sources, assumptions, governing load or process condition, failure consequences, selected concept, verification method and acceptance criterion. Mark every numerical input as project requirement, verified supplier data, measured value, calculation output or assumption. Review the weakest evidence first. If an assumption can change safety, compliance, interchangeability or capacity, it must be resolved before release rather than buried in a calculation note.

Evidence class	Question	Release expectation
Requirement	What must the design do and under which conditions?	Approved and traceable
Input	Where did the load, property, tolerance or process limit come from?	Source, unit and revision recorded
Analysis	Which model and assumptions connect input to result?	Checkable calculation or simulation
Verification	How will conformity be demonstrated?	Method and acceptance criterion agreed
Validation	Will the solution work for intended users and conditions?	Representative use evidence

Common failure modes and recovery actions

1. Watch for

Starting detailed design before interfaces and operating limits are agreed.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Using catalogue or typical values as though they were certified project inputs.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Checking nominal performance while ignoring tolerances, degradation and foreseeable misuse.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Confusing verification of requirements with validation of user need.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Releasing drawings or procedures without configuration, inspection and change controls.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.