What's the difference between DXF and P21? 6 points to check before delivery
By LRTK Team (Lefixea Inc.)
Table of contents
• Why DXF and P21 are easy to confuse
• Point 1 Their original roles are different
• Point 2 Their approaches to drawing fidelity differ
• Point 3 How they carry attribute information and drawing rules differs
• Point 4 They are suited to different recipients and scopes of work
• Point 5 Ease of modification and operational methods differ
• Point 6 Items to check before delivery differ
• Preparing field data is as important as choosing the format
Why DXF and P21 are easy to confuse
When you are involved in exchanging drawing data, there are many situations where you simply export in the format requested by the other party without fully understanding the difference between DXF and P21. Both are commonly recognized as formats used for drawing exchange, and since lines and text look similar on the screen, they are often confused in practice. However, what becomes important at the delivery or inspection stage is not only whether the file can be opened and viewed. You need to consider how accurately things are reproduced, how much attribute information and rules are preserved, and whether the format meets the recipient's requirements.
In short, DXF is a general exchange format that makes it easy to transfer drawings across a wide range of environments, while P21 tends to perform well where standardized drawing exchange is emphasized. DXF is flexible and easy to use but can produce variability depending on operational practices; P21, because it assumes rule-based exchange, tends to ensure consistency as a format. In other words, they are not simply in an upper- or lower-compatibility relationship; understanding them as formats with different purposes prevents confusion in practice.
For those responsible who want to determine whether “DXF is sufficient” or “P21 is necessary,” what matters is not knowing the format name but organizing which process the format is suited to. Appropriate selection depends on practical context: design-stage exchanges, data interchange with subcontractors, public deliverables, future reuse, drawing re-editing, integration with coordinate-attached data, etc. From here, we will organize the differences between DXF and P21 from a practical perspective, focusing on six points to check before delivery.
Point 1 Their original roles are different
The first thing to grasp is that although DXF and P21 may look similar, their original roles are different. DXF has long been used as a format to facilitate exchange of geometric data between different drafting environments and different software. Its uses are very broad: exchanges between designers, simple handovers with subcontractors or partners, intermediate outputs for manufacturing data, referencing and importing existing drawings, and more. In other words, DXF's strength is being readable in as many environments as possible; its high versatility is its defining feature.
On the other hand, P21 is easier to understand if you think of it as a format that emphasizes stable drawing exchange under a set of rules. Operationally, it's not enough that the drawing can simply be viewed; P21 is used in contexts that aim for more standardized exchanges that include line types and text, the meaning of drawing elements, and overall drawing consistency. P21 is more likely to be adopted when recipients emphasize format uniformity and long-term reuse.
This difference is easier to understand if you translate it into everyday work sensibilities. DXF is “a format that makes it easy for the recipient to open and work with the drawing even if their environment varies somewhat.” P21 is “a format that hands over drawings under defined rules so that consistency is easier to maintain downstream.” The former prioritizes flexibility; the latter prioritizes uniformity.
Therefore, when considering whether a format is suited to design-stage exchanges or to formal delivery and inspection responses, the difference in roles becomes clear. If you want to quickly adjust drawings within your organization or with partners, DXF is convenient; if the recipient requires a well-prepared submission format, P21 can be more reassuring. Understanding this role distinction first makes subsequent decisions less ambiguous.
Point 2 Their approaches to drawing fidelity differ
Next important is their approach to drawing fidelity. In practice, when the same drawing file is opened at the recipient's site, issues can occur such as lines appearing thicker than intended, text positions shifting slightly, hatch patterns breaking, or grouped entities not behaving as intended. If you conclude “the file opened, so there’s no problem,” you may face rework after delivery.
While DXF is highly versatile, it can be susceptible to differences in the recipient’s environment. The appearance of lines and text, block-like groupings, dimension representations, and handling of auxiliary elements may not be reproduced exactly the same. Of course, with proper operational procedures, DXF can enable stable exchange. However, differences in user settings and import methods often affect the results, and much of the reproducibility may rely on human operational adjustments.
By contrast, P21 emphasizes passing drawing elements according to standard rules rather than just appearance, so it tends to stabilize reproduction after handover. Especially when drawings circulate across multiple organizations or long processes, the demand to minimize differences between recipients grows stronger. In such situations, rule-based, standardized formats like P21 provide greater confidence as deliverables.
Note, however, that P21 does not guarantee that nothing will break. If the source drawing is poorly constructed, problems remain regardless of the target format. Inconsistent text styles, ambiguous layer practices, mixed scale approaches, or leftover unnecessary or duplicate elements limit the quality after conversion. In other words, differences in reproducibility depend not only on format but also heavily on how well the source data is prepared.
What you should really check before delivery is not whether it looks fine on your screen, but whether it is a readable drawing when opened under conditions close to the recipient’s assumptions. Keeping this perspective makes choosing between DXF and P21 much more practical.
Point 3 How they carry attribute information and drawing rules differs
The third point is how attribute information and drawing rules are carried. A drawing is not merely a collection of lines. Practical drawings include meanings such as which lines are outlines, which are centerlines, which text represents dimensions, and which elements are parts of structures. Even if appearance is similar, if meaning is not correctly conveyed, interpretations in downstream processes will diverge.
DXF can handle layers, colors, line types, text, and geometry widely, so it is very convenient in practice. For designers, it allows flexible creation, easy editing, and many possible recipients. However, decisions about layer naming, color usage, and how to organize the meaning of attributes tend to depend on operational agreements. That is, the more broadly DXF can represent things, the more it relies on separate operational rules; without clear rules, different people will create drawings differently.
P21 is effective where you want to suppress such variability. Because it assumes standardized handover, it is easier to bring a unified approach to handling drawing elements and organizing attribute information. In practice, drawings are sometimes reused by other departments or organizations after submission; at that time, what matters is not only “how this drawing looks” but that “what this element means” is correctly conveyed. P21 is a format that emphasizes that point.
This difference greatly affects how drawings are used after delivery. For example, when considering inspection, storage, re-editing, future renovation design, quantity checks, or integration with various ledgers, drawings with poorly organized semantic information become more difficult to handle. DXF is convenient for short-term exchange, but for long-term reuse the weakness of operation-dependent practices becomes evident. P21 is stronger for projects that want stable operation including the meanings embedded in drawings.
Therefore, before delivery, you should review not only the file extension but also whether layer names, element classification, text rules, and the meaning assigned to lines conform to the recipient’s requirements. The difference between formats affects this aspect more than appearance.
Point 4 They are suited to different recipients and scopes of work
The fourth point is which recipients and scopes of work each format is suited to. If you do not understand this, you may be able to export the file but end up having it returned by the recipient. What causes trouble for field personnel is not format conversion itself but the mismatch between submission rules and on-site operations.
DXF is suited to situations where relatively flexible data exchange is allowed. In contexts where speed and compatibility are prioritized—early-stage design drafts, coordination with partners, exchange of reference drawings, import of existing drawings, and intermediate data for machining or analysis—DXF is useful. Even if you don’t know which environment the recipient uses, the file is likely to open, making it a good entry point for collaboration.
P21, on the other hand, is suited to situations that require organized operations covering format uniformity through to post-delivery storage and reuse. Especially when not only appearance but rule-based consistency and reproducibility are emphasized, P21 is more likely to be chosen. When there are multiple recipients, the project may be opened by different personnel in the future, or when interpretation of drawings directly affects downstream processes, standardized formats become more valuable.
It is important to understand that this is not simply “DXF is informal and P21 is formal.” For example, DXF may be sufficient internally but P21 may be required for the final delivery. Conversely, if the recipient does not require P21, forcing conversion to P21 may make internal editing more difficult. The important thing is not which is superior but what to prioritize at each stage.
In practice, many organizations manage editable formats during drawing work and convert to the specified submission format at formal delivery. With this approach, DXF and P21 are not opposing formats but complementary choices used according to the process. To avoid last-minute problems before delivery, confirm recipient requirements early in the project and decide data management methods across intermediate steps.
Point 5 Ease of modification and operational methods differ
The fifth point is the difference in ease of modification and day-to-day operations. This is very important for field personnel because drawings are not created once and finished; they are subject to revisions, stakeholder reviews, and replacements. When choosing a format, you must consider not only how it will look at delivery but how many revisions will occur before that.
DXF’s major advantage is its high flexibility for modification and reuse. It opens easily in multiple environments and is geometry-based, making it easy to handle for repeated fine adjustments and minor changes. In cases where you want to slightly correct a drawing received from an external vendor, reuse part of another drawing, or use it as a provisional study drawing, DXF’s ease of handling pays off. This flexibility is more valuable on-site than you might imagine.
However, the very accessibility of DXF makes it prone to rule deterioration. If layer structures become disorganized, text settings become mixed, or unnecessary elements accumulate, initial convenience can lead to higher costs at the delivery stage to tidy things up. A common failure in DXF operations is that prioritizing editability reduces the overall consistency of drawings. In projects touched by multiple people, unclear maintenance criteria cause headaches at final checks.
P21 is more suitable for handing over a consistently prepared state rather than for free daily editing. Using it at conversion or delivery milestones makes it easier to align drawings to a standard state. In other words, P21 favors delivery integrity over mid-process freedom.
Therefore, in practice it is important to separate the format used to manage source data from the delivery format. Operate in an editable environment during work, and convert to P21 while checking rules before delivery to balance productivity and delivery quality. Conversely, focusing too much on the final delivery format from the start makes mid-process edits harder and slows field speed. The choice of format should include consideration of the editing workflow.
Point 6 Items to check before delivery differ
The sixth point is that the checklist before delivery differs. A common oversight in many workplaces is feeling reassured by matching only the file extension. Whether DXF or P21, if the submission does not meet the recipient’s conditions, it will be returned. Moreover, reasons for return are often related to drawing content or consistency rather than the simple file format.
When preparing a DXF for delivery, first check whether appearance breaks when opened. Typical items include garbled text, changes in line types, missing hatches, dimension errors, coordinate shifts, leftover unnecessary geometry, and insufficient layer organization. Given the recipient may use a different environment, it is also important to ensure your creation method is not overly idiosyncratic. A state that looks correct only in your environment is insufficient as delivery quality.
When preparing a P21 for delivery, in addition to appearance checks, you need to more strictly review the drawing as a standardized document. Check classification, element handling, rules for lines and text, missing necessary information, and contamination by extraneous elements—i.e., whether the data conforms to the format’s expectations. It is not enough that conversion succeeded; you must confirm that the submission data makes sense as deliverable material.
Additionally, an issue you cannot ignore in either format is coordinates and scale. Even if the drawing opens, if the handling of reference points and origin, unit interpretation, or assumed scale is mismatched, significant errors will occur downstream. Especially when using surveying results, construction drawings, as-built management, staking out, or overlaying point clouds and photogrammetry results, it is essential that coordinate concepts align as well as the drawing format. If this is off, the data becomes unusable in practice, regardless of whether it is DXF or P21.
For the final check before delivery, do not leave it solely to the person converting formats; review from the standpoint of those who will actually use the drawing. Designers, construction managers, surveyors, contractors, and clients each focus on slightly different points. Understanding format differences and checking what the recipient prioritizes is the most practical way to reduce rejections.
Preparing field data is as important as choosing the format
As you have seen, the difference between DXF and P21 is not just an extension. DXF’s strengths are versatility and flexibility; P21’s strengths are standardized handover and consistency. Which to choose depends on the recipient, the process, whether reuse is expected, revision frequency, and whether coordinate-attached operations are involved. What’s truly important before delivery is not memorizing format names but clarifying what must be maintained for that project.
Attention often focuses only on format selection, but in practice the upstream field data acquisition is equally important. For example, if on-site position information is ambiguous, no matter how the drawing format is standardized, you will struggle later with coordinate consistency. If photos, point clouds, as-built records, and reference position records are scattered, harmonizing delivery formats won’t prevent operationally difficult data. In other words, choosing a delivery format should be considered together with the accuracy of field data acquisition.
If you regularly organize the relationships among drawings, coordinates, site photos, and point clouds, the ease of downstream handling will differ significantly whether you use DXF or P21. Establishing a workflow that confirms design drawings on site, secures construction positions, and records in a reusable way stabilizes delivery quality. Preventing delivery troubles is not achieved solely by format conversion; it requires viewing the process from field acquisition through data organization as a single flow.
In that sense, for sites that want to handle the relationship between drawings and site positions more accurately, there is value in adopting systems like LRTK early. As an iPhone-mounted GNSS high-precision positioning device, LRTK can streamline on-site position acquisition and help link drawings, positioning results, and photo records to downstream processes. When considering whether to deliver in DXF or P21, having well-prepared upstream field data increases drawing reliability and makes pre-delivery checks easier. Correctly understanding format differences while also reviewing the quality of field-collected data is the most effective practice in the field.
Next Steps:
Explore LRTK Products & Workflows
LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.
LRTK supercharges field accuracy and efficiency
The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.


